Triple
T29537624
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 210 (California) |
E749392
|
entity |
| Predicate | terminusEastAt |
P3569
|
FINISHED |
| Object | junction with Interstate 10 |
—
|
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: junction with Interstate 10 | Statement: [Interstate 210 (California), terminusEastAt, junction with Interstate 10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminusEastAt Context triple: [Interstate 210 (California), terminusEastAt, junction with Interstate 10]
-
A.
terminusEast
chosen
Indicates that one entity serves as the eastern endpoint or final stop of another entity, such as a route, line, or path.
-
B.
easternTerminusLocatedOn
Indicates that the eastern endpoint of a route, line, or path is situated on or at a specified feature or location.
-
C.
terminusProvinceEast
Indicates that something’s eastern endpoint or terminus lies within a particular province.
-
D.
terminusCitySoutheast
Indicates that something serves as the southeastern terminus or endpoint of a route, line, or connection in a particular city.
-
E.
terminusNortheast
Indicates that one entity serves as the northeastern terminus or endpoint of another entity (such as a route, line, or path).
- 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_69f0bd47abb081909bd6e6a33d770fd8 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f6bbf6e33c819086e5176d64e7a614 |
completed | May 3, 2026, 3:07 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6b1e6c8190adf9d6a257e0b744 |
completed | May 3, 2026, 3 a.m. |
Created at: April 28, 2026, 4:59 p.m.