Triple
T424122
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Interstate 80 |
E8167
|
entity |
| Predicate | westernTerminusDetail |
P13603
|
FINISHED |
| Object | U.S. Route 101 in San Francisco, California |
—
|
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: U.S. Route 101 in San Francisco, California | Statement: [Interstate 80, westernTerminusDetail, U.S. Route 101 in San Francisco, California]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: westernTerminusDetail Context triple: [Interstate 80, westernTerminusDetail, U.S. Route 101 in San Francisco, California]
-
A.
westernTerminusNear
Indicates that the western endpoint of one entity is located close to another entity.
-
B.
locatedWestOf
Indicates that one entity is positioned geographically to the west of another entity.
-
C.
terminusEast
Indicates that one entity serves as the eastern endpoint or final stop of another entity, such as a route, line, or path.
-
D.
locatedNorthwestOf
Indicates that one entity is positioned to the northwest of another entity in space or geography.
-
E.
liesNorthwestOf
Indicates that one entity is located to the northwest of another entity, combining both a more northern and more western position relative to it.
- 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_69a2e7f1d1bc81909cf2dc9754a3c334 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2eed3e4cc8190ba6aff3bd1adb06f |
completed | Feb. 28, 2026, 1:34 p.m. |
| PD | Predicate disambiguation | batch_69a2edd5439c8190aea661b8b4aa51e9 |
completed | Feb. 28, 2026, 1:29 p.m. |
| PDg | Predicate description generation | batch_69a2ee8b56d08190bd625626353d01b4 |
completed | Feb. 28, 2026, 1:32 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.