Triple
T31807161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | US 250 Business |
E811903
|
entity |
| Predicate | runsAlongCorridorOf |
P113763
|
FINISHED |
| Object | U.S. Route 250 |
—
|
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: U.S. Route 250 | Statement: [US 250 Business, runsAlongCorridorOf, U.S. Route 250]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runsAlongCorridorOf Context triple: [US 250 Business, runsAlongCorridorOf, U.S. Route 250]
-
A.
followedCorridor
chosen
Indicates that an entity moved along and stayed within the path of a corridor from one point to another.
-
B.
focusesOnCorridor
Indicates that an action, attention, or process is directed specifically toward a corridor or passageway.
-
C.
hasCorridor
Indicates that one entity includes, is connected by, or provides access through a corridor to another entity.
-
D.
inCorridor
Indicates that one entity is located within or inside a corridor relative to another spatial context or reference.
-
E.
corridorFunction
Indicates that one entity serves as a corridor or passageway functionally connecting or providing access between other spaces or areas.
- 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_69f348e70d188190b4637c5509f81274 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6afebd7ec8190ab696f363d84abf0 |
completed | May 3, 2026, 2:16 a.m. |
| PD | Predicate disambiguation | batch_69f6aca3dedc81908b519d53d2909868 |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:43 p.m.