Triple
T7848070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southeastern Wisconsin |
E181969
|
entity |
| Predicate | majorUSHighway |
P385
|
FINISHED |
| Object | U.S. Route 41 |
—
|
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: U.S. Route 41 | Statement: [Southeastern Wisconsin, majorUSHighway, U.S. Route 41]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: majorUSHighway Context triple: [Southeastern Wisconsin, majorUSHighway, U.S. Route 41]
-
A.
stateHighwayServedBy
Indicates that a particular state highway is provided service or coverage by a specified transportation route, agency, or facility.
-
B.
isIntercityHighway
Indicates that a given road segment functions as a highway connecting different cities or urban areas.
-
C.
hasMajorHighway
chosen
Indicates that a location or area is served by or directly connected to a major highway route.
-
D.
isHighestNumberedInterstateInUnitedStates
Indicates that the subject interstate has the highest route number of all interstate highways in the United States.
-
E.
motorwayServedBy
Indicates that a motorway is connected to or accessed by a particular service facility, route, or transport service.
- 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_69ca8285d6488190a95d4c02d7354b53 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb18e7f5988190808ae4dcfbc06991 |
completed | March 31, 2026, 12:44 a.m. |
| PD | Predicate disambiguation | batch_69cae92180f88190ae3d44c3de7adc93 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:49 p.m.