Triple
T34218745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Mexico State Road 209 |
E877865
|
entity |
| Predicate | terminusAType |
P9111
|
FINISHED |
| Object | southern 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: southern terminus | Statement: [New Mexico State Road 209, terminusAType, southern terminus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminusAType Context triple: [New Mexico State Road 209, terminusAType, southern terminus]
-
A.
terminusType
chosen
Indicates the specific kind or role of an endpoint or terminal within a route, network, or process.
-
B.
terminus
Indicates that one entity serves as the final endpoint or stopping place for another entity’s movement, route, or process.
-
C.
terminusFeature
Indicates that a specific physical or structural feature is located at, marks, or characterizes the endpoint or terminus of something.
-
D.
terminusTowards
Indicates that one entity serves as the endpoint or directional terminus oriented toward another entity.
-
E.
terminusDescription
Indicates the textual description that characterizes the endpoint or final stop of a route, path, or process.
- 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_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf769338819092a5f42653dcc956 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 1, 2026, 1:55 a.m.