Triple
T21616902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kingsbury Grade |
E533466
|
entity |
| Predicate | hasDirectionEndpoints |
P144794
|
FINISHED |
| Object | western terminus near Stateline, Nevada |
—
|
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: western terminus near Stateline, Nevada | Statement: [Kingsbury Grade, hasDirectionEndpoints, western terminus near Stateline, Nevada]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDirectionEndpoints Context triple: [Kingsbury Grade, hasDirectionEndpoints, western terminus near Stateline, Nevada]
-
A.
hasRouteDirection
Indicates that a specified route is associated with a particular travel direction (e.g., inbound, outbound, northbound).
-
B.
hasDirectionType
Indicates that something possesses or is associated with a specific type or category of direction.
-
C.
hasNumberOfDirections
Indicates that an entity is associated with a specific count of possible directions or orientations.
-
D.
containsDirectionOf
Indicates that one entity includes or encompasses the directional orientation or path associated with another entity.
-
E.
hasDirectionLabels
Indicates that a subject is associated with one or more labels specifying directions or orientations.
- 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_69e0c46411108190bba0d4176dffc9f3 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef3bab865081908bc7d7b1824415ac |
completed | April 27, 2026, 10:34 a.m. |
| PD | Predicate disambiguation | batch_69e69665fe8c8190af7e38785db188b2 |
completed | April 20, 2026, 9:11 p.m. |
| PDg | Predicate description generation | batch_69e69b4aa2b48190830107391e81571a |
completed | April 20, 2026, 9:31 p.m. |
Created at: April 16, 2026, 6:34 p.m.