Triple
T18321141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pennsylvania Route 3 |
E438881
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | numbered highway in Pennsylvania |
C40347
|
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 highway in Pennsylvania Context triple: [Pennsylvania Route 3, instanceOf, numbered highway in Pennsylvania]
-
A.
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.
-
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 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.
-
D.
numbered highway in New York
A numbered highway in New York is a designated, signed roadway within the state’s transportation network, identified by a unique route number and maintained by a specific governmental authority (state, federal, or local).
-
E.
numbered highway in Illinois
A numbered highway in Illinois is a designated state, U.S., or interstate route within Illinois marked by an official route number and maintained for public vehicular travel.
- F. None of above. chosen
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_69d8b916a2d081909e249e4902f6aad9 |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:36 a.m.