Triple
T9085260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colonial Parkway |
E217734
|
entity |
| Predicate | stateRouteType |
P1019
|
FINISHED |
| Object | unsigned federal parkway |
—
|
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: unsigned federal parkway | Statement: [Colonial Parkway, stateRouteType, unsigned federal parkway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateRouteType Context triple: [Colonial Parkway, stateRouteType, unsigned federal parkway]
-
A.
stateRouteDesignation
Indicates the specific state-level route number or designation assigned to a roadway within a state highway system.
-
B.
roadType
chosen
Indicates the classification or category of a road based on its functional or physical characteristics.
-
C.
roadServed
Indicates that a road is provided with necessary services or infrastructure support by a responsible entity.
-
D.
notableRouteType
Indicates that a route is particularly significant or well-known for a specific type or category (e.g., scenic, historic, commercial).
-
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_69ca83d7a0388190ba1af89ed7ba36f9 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc960d0b008190b0e9e61fac45101d |
completed | April 1, 2026, 3:50 a.m. |
| PD | Predicate disambiguation | batch_69cc65fa79bc81908b46f05c8bba920f |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:13 p.m.