Triple
T26043008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SR 2 |
E647747
|
entity |
| Predicate | westernTerminusHighway |
P117355
|
FINISHED |
| Object | California State Route 1 |
—
|
NE NERFINISHED |
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: California State Route 1 | Statement: [SR 2, westernTerminusHighway, California State Route 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: westernTerminusHighway Context triple: [SR 2, westernTerminusHighway, California State Route 1]
-
A.
westernTerminusDetail
Indicates the specific endpoint location or characteristics associated with the western terminus of a route or linear feature.
-
B.
westernTerminusConnectsTo
chosen
Indicates that the western endpoint or terminus of one route, line, or path is directly connected to another specified route, line, or location.
-
C.
westernTerminusNear
Indicates that the western endpoint of one entity is located close to another entity.
-
D.
westernTerminusCrosses
Indicates that the western endpoint of a route, line, or path intersects or passes over another feature or boundary.
-
E.
westernTerminusBridge
Indicates that a bridge serves as the western terminus or endpoint of a route, line, or infrastructure segment.
- 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_69e77e8c88f08190858c4c81bd2e1b9a |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f606588684819087b366450d7c4fa9 |
completed | May 2, 2026, 2:12 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fba5248190945acf1561280799 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 22, 2026, 9:08 a.m.