Triple
T23904651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Route 240 |
E601154
|
entity |
| Predicate | partOfCorridorNowServedBy |
P85888
|
FINISHED |
| Object | Interstate 270 |
—
|
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: Interstate 270 | Statement: [U.S. Route 240, partOfCorridorNowServedBy, Interstate 270]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfCorridorNowServedBy Context triple: [U.S. Route 240, partOfCorridorNowServedBy, Interstate 270]
-
A.
isPartOfCorridorSystem
chosen
Indicates that one entity forms a component or segment within a larger interconnected corridor system.
-
B.
hasServiceOnCorridor
Indicates that a service operates along, or is provided on, a specific corridor or route.
-
C.
primaryCorridorServed
Indicates that a corridor is the main route or pathway served by a given service, facility, or entity.
-
D.
hasCorridor
Indicates that one entity includes, is connected by, or provides access through a corridor to another entity.
-
E.
corridorType
Indicates the specific kind or classification of a corridor associated with an entity or location.
- 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_69e295364a488190bcac702e9bb7f764 |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1cde13e88819086bbd0bc4a5b6a36 |
completed | April 29, 2026, 9:22 a.m. |
| PD | Predicate disambiguation | batch_69f1614e24b48190a1c8fb5b7c75ee0f |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:26 p.m.