Triple
T29537622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 210 (California) |
E749392
|
entity |
| Predicate | terminusWestIn |
P54994
|
FINISHED |
| Object | Los Angeles |
E715
|
NE 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: Los Angeles | Statement: [Interstate 210 (California), terminusWestIn, Los Angeles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminusWestIn Context triple: [Interstate 210 (California), terminusWestIn, Los Angeles]
-
A.
terminusWestConnection
Indicates that one entity serves as the western endpoint where it connects to another entity or route.
-
B.
terminusWestNear
Indicates that the western terminus of one entity is located near the western terminus of another entity.
-
C.
terminusCityWest
chosen
Indicates that a route, line, or service has its western terminus located in the specified city.
-
D.
terminusWestCountry
Indicates that something serves as the western endpoint or final stop of a route, line, or connection within the West Country region.
-
E.
terminusWestBorough
Indicates that something serves as the western terminus or endpoint of a route, line, or connection at a place called Borough.
- F. None of above.
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_69f0bd47abb081909bd6e6a33d770fd8 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69f6b903538481909cffcb6cc1cc0e70 |
completed | May 3, 2026, 2:54 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a260bff6b688190b82b62770b2e3d99 |
completed | June 8, 2026, 12:25 a.m. |
| PD | Predicate disambiguation | batch_69f6b626120c819097c9ad04487570d7 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 28, 2026, 4:59 p.m.