Triple
T1283429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mission San Francisco Solano |
E27377
|
entity |
| Predicate | positionInMissionChain |
P23808
|
FINISHED |
| Object | last-established |
—
|
LITERAL FINISHED |
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: last-established | Statement: [Mission San Francisco Solano, positionInMissionChain, last-established]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: positionInMissionChain Context triple: [Mission San Francisco Solano, positionInMissionChain, last-established]
-
A.
orderInMissionChain
chosen
Indicates the position or sequence of a mission within a larger mission chain or progression.
-
B.
missionChainOrder
Indicates the sequential ordering relationship between missions within a mission chain, specifying which mission must occur before another.
-
C.
chainPosition
Indicates the position or rank an entity occupies within an ordered chain or sequence relative to other entities.
-
D.
positionInFormation
Indicates the relative place or role an entity occupies within an organized formation or arrangement.
-
E.
positionInState
Indicates that one entity occupies or holds a specific position, role, or status within a particular state or condition of another entity.
- 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_69a496d3710c8190955dee8bc0dacb50 |
completed | March 1, 2026, 7:43 p.m. |
| NER | Named-entity recognition | batch_69a4c0b599ac819096fca9ada294d939 |
completed | March 1, 2026, 10:41 p.m. |
| PD | Predicate disambiguation | batch_69a4bee276d8819092f71c5a1140bb61 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:50 p.m.