Triple
T37625992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State Road 50 |
E936209
|
entity |
| Predicate | crossesInterstateHighway |
P141439
|
FINISHED |
| Object | Interstate 75 |
—
|
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: Interstate 75 | Statement: [State Road 50, crossesInterstateHighway, Interstate 75]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crossesInterstateHighway Context triple: [State Road 50, crossesInterstateHighway, Interstate 75]
-
A.
crossedByHighway
Indicates that a highway passes across or through the extent of a given entity or area.
-
B.
interstateHighwayPassesThrough
chosen
Indicates that a specific interstate highway physically traverses or runs through the geographic area or jurisdiction of a given place.
-
C.
connectsToInterstate
Indicates that one roadway, route, or location has a direct connection or access point to an interstate highway.
-
D.
expresswayInterchange
Indicates a road connection where an expressway intersects with another road or expressway, allowing vehicles to transfer between them.
-
E.
primaryInterstateHighway
Indicates that the subject is designated as a primary (main) interstate highway within the interstate highway system.
- 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_69f76ed24820819081bafd36e9088701 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fd2a215d6c8190a1a428ccaee603f1 |
completed | May 8, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69fd28ef19688190bb8370f2812a43e7 |
completed | May 8, 2026, 12:06 a.m. |
Created at: May 3, 2026, 4:18 p.m.