Triple
T1283430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mission San Francisco Solano |
E27377
|
entity |
| Predicate | relativeLocationInMissionChain |
P23578
|
FINISHED |
| Object | northernmost |
—
|
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: northernmost | Statement: [Mission San Francisco Solano, relativeLocationInMissionChain, northernmost]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relativeLocationInMissionChain Context triple: [Mission San Francisco Solano, relativeLocationInMissionChain, northernmost]
-
A.
hasRelativeLocation
Indicates that one entity is positioned in space in relation to another entity’s location.
-
B.
relativeLocationOnIsland
Indicates a spatial relationship where one entity’s position is described relative to another entity specifically in the context of being on an island.
-
C.
relativePosition
chosen
Indicates the spatial relationship of one entity’s location with respect to another entity’s position.
-
D.
orderInMissionChain
Indicates the position or sequence of a mission within a larger mission chain or progression.
-
E.
relativePositionOnCourse
Indicates the positional relationship of one participant or object relative to another along a defined course or route.
- 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.