Triple
T24449097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haast Pass |
E616481
|
entity |
| Predicate | roadCompleted |
P156163
|
FINISHED |
| Object | 1965 |
—
|
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: 1965 | Statement: [Haast Pass, roadCompleted, 1965]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roadCompleted Context triple: [Haast Pass, roadCompleted, 1965]
-
A.
routeCompleted
Indicates that a specified route has been fully traversed or finished by the relevant entity or process.
-
B.
completedAsFreeway
Indicates that a roadway segment has been fully constructed or upgraded to meet freeway standards, typically implying controlled access and grade-separated intersections.
-
C.
completedAsContinuousMotorway
Indicates that a road segment has been fully built and functions as an unbroken, continuously drivable motorway.
-
D.
roadCheckpointFor
Indicates that a specific checkpoint is designated for monitoring or controlling access along a particular road or route.
-
E.
mappingCompleted
Indicates that a previously initiated mapping process between entities has been successfully finished.
- F. None of above. chosen
Provenance (4 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_69e2d7edca608190aafefc8877a1b4da |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f298562c6c8190a7374508f7237be2 |
completed | April 29, 2026, 11:46 p.m. |
| PD | Predicate disambiguation | batch_69f287d3237c819099559c00f83131d8 |
completed | April 29, 2026, 10:36 p.m. |
| PDg | Predicate description generation | batch_69f28f4d978c81908310c01def2514cc |
completed | April 29, 2026, 11:07 p.m. |
Created at: April 18, 2026, 2:18 a.m.