Triple
T27357313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Route 211 and Skyline Drive |
E685718
|
entity |
| Predicate | stateHighwayComponent |
P88251
|
FINISHED |
| Object | U.S. Route 211 |
—
|
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 211 | Statement: [U.S. Route 211 and Skyline Drive, stateHighwayComponent, U.S. Route 211]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateHighwayComponent Context triple: [U.S. Route 211 and Skyline Drive, stateHighwayComponent, U.S. Route 211]
-
A.
nationalHighwayNetworkState
Indicates that a state is part of, or associated with, the national highway network.
-
B.
containsStateHighway
Indicates that a geographic area or region includes within its boundaries at least one designated state highway.
-
C.
stateHighwayServedBy
Indicates that a particular state highway is provided service or coverage by a specified transportation route, agency, or facility.
-
D.
stateHighwayDesignationIn
chosen
Indicates that a roadway has been designated as a state highway within a specified jurisdiction or region.
-
E.
stateHighwayConnectivity
Indicates that there is a transportation connection or linkage between locations via a designated state highway.
- 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_69ef14887c288190931b8431fdbf53c4 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
Created at: April 27, 2026, 11:52 a.m.