Triple
T6520613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Carolina Highway 200 |
E148369
|
entity |
| Predicate | isImportantRegionalRoute |
P36293
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [North Carolina Highway 200, isImportantRegionalRoute, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isImportantRegionalRoute Context triple: [North Carolina Highway 200, isImportantRegionalRoute, true]
-
A.
isMajorRoadIn
Indicates that a road is classified as a major road within a specified geographic area or jurisdiction.
-
B.
isIntercityHighway
Indicates that a given road segment functions as a highway connecting different cities or urban areas.
-
C.
isRegionalCrossroads
Indicates that a place serves as a key junction where multiple regional routes, networks, or areas intersect and connect.
-
D.
hasMajorTransportationRole
chosen
Indicates that an entity plays a primary or significant role in providing or supporting transportation services or infrastructure.
-
E.
isSuburbanRouteOf
Indicates that a given route functions as a suburban segment or service line belonging to, or operating as part of, a larger primary route or network.
- 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_69c687e68e748190baceb9298f32d3ed |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ad9431f081909b14b3df3414a55f |
completed | March 27, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69c68abbc7148190a8270d47fe10cc31 |
completed | March 27, 2026, 1:48 p.m. |
Created at: March 27, 2026, 1:45 p.m.