Triple
T17734589
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | California State Route 270 |
E442679
|
entity |
| Predicate | endpointTypeAtWest |
P51120
|
FINISHED |
| Object | highway junction |
—
|
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: highway junction | Statement: [California State Route 270, endpointTypeAtWest, highway junction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endpointTypeAtWest Context triple: [California State Route 270, endpointTypeAtWest, highway junction]
-
A.
hasTerminusWest
chosen
Indicates that something has its western endpoint, terminus, or final stop at the referenced entity.
-
B.
terminusEast
Indicates that one entity serves as the eastern endpoint or final stop of another entity, such as a route, line, or path.
-
C.
endPoint
Indicates the terminal location, limit, or final state reached by an object, process, or path in a given relationship or action.
-
D.
boundaryTypeWest
Indicates the type or nature of the boundary that exists on the western side of an entity or area.
-
E.
endpointOnPeninsula
Indicates that one endpoint of an object, path, or feature lies on or within the bounds of a peninsula.
- 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_69d8b9ed3a2081909b2ec0d4dd2f4c37 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e478e98a00819089490be2aa36873d |
completed | April 19, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69e3cde815e08190881972e2d80d151e |
completed | April 18, 2026, 6:31 p.m. |
Created at: April 10, 2026, 10:08 a.m.