Triple
T32305643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Juaneño |
E825355
|
entity |
| Predicate | missionFounded |
P74642
|
FINISHED |
| Object | Mission San Juan Capistrano (1776) |
—
|
NE NERFINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Mission San Juan Capistrano (1776) | Statement: [Juaneño, missionFounded, Mission San Juan Capistrano (1776)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missionFounded Context triple: [Juaneño, missionFounded, Mission San Juan Capistrano (1776)]
-
A.
missionTypeEstablished
Indicates that a specific type or category of mission has been formally defined and put into effect.
-
B.
establishedMissionFor
chosen
Indicates that an entity formally created or set up a specific mission, assigning it purpose or objectives.
-
C.
missionFirst
Indicates that one entity prioritizes accomplishing a mission or objective above other considerations or interests.
-
D.
missionOrigin
Indicates the place, organization, or context from which a mission is initiated or originates.
-
E.
missionStart
Indicates the point in time or event at which a mission or task officially begins.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69f349115304819084ee91d345b6c8aa |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6d16f5cb881908eed141afaaa0b51 |
completed | May 3, 2026, 4:39 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe45554819089cbbd538d992132 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 12:45 a.m.