Triple
T25567039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DE 273 |
E640865
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | numbered route in Delaware |
C48855
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: numbered route in Delaware Context triple: [DE 273, instanceOf, numbered route in Delaware]
-
A.
road in Delaware
chosen
A road in Delaware is a paved or unpaved public or private thoroughfare within the state’s boundaries that facilitates vehicular and pedestrian travel between locations.
-
B.
numbered highway in Maryland
A numbered highway in Maryland is a designated roadway within the state’s transportation network, identified by a unique route number and maintained by the appropriate state or federal agency to facilitate regional and interstate travel.
-
C.
numbered highway in Pennsylvania
A numbered highway in Pennsylvania is a designated roadway within the state’s transportation network identified by a unique route number and maintained by state or federal authorities for regional and interstate travel.
-
D.
numbered highway in New Jersey
A numbered highway in New Jersey is a designated roadway within the state’s transportation network, identified by a unique route number and maintained by state or federal agencies to facilitate regional and interstate travel.
-
E.
numbered highway in New Hampshire
A numbered highway in New Hampshire is a designated state, U.S., or interstate route within New Hampshire’s road network, identified by a unique number and maintained by the appropriate transportation authority.
- F. None of above.
Provenance (1 batch)
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_69e75dc1beb08190bac7d76b8d6e7bc4 |
completed | April 21, 2026, 11:21 a.m. |
Created at: April 21, 2026, 3:50 p.m.