Triple
T34218746
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Mexico State Road 209 |
E877865
|
entity |
| Predicate | terminusBType |
P9111
|
FINISHED |
| Object | northern terminus |
—
|
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: northern terminus | Statement: [New Mexico State Road 209, terminusBType, northern terminus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminusBType Context triple: [New Mexico State Road 209, terminusBType, northern terminus]
-
A.
terminusType
chosen
Indicates the specific kind or role of an endpoint or terminal within a route, network, or process.
-
B.
terminusBState
Indicates the state or condition of the entity that serves as the endpoint (B terminus) of a connection, process, or relationship.
-
C.
terminusBLocation
Indicates the location at which the B end or second endpoint of something (such as a route, connection, or segment) is situated.
-
D.
terminus
Indicates that one entity serves as the final endpoint or stopping place for another entity’s movement, route, or process.
-
E.
terminusTowards
Indicates that one entity serves as the endpoint or directional terminus oriented toward 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_69f349b0b4bc819088c1552424089ee9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 1, 2026, 1:55 a.m.