Triple
T15136307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Detroit area freeway network |
E361563
|
entity |
| Predicate | hasComponent |
P35
|
FINISHED |
| Object | M-14 |
E267563
|
NE 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: M-14 | Statement: [Detroit area freeway network, hasComponent, M-14]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: M-14 Context triple: [Detroit area freeway network, hasComponent, M-14]
-
A.
M-14
chosen
M-14 is a state highway in southeastern Michigan that serves as a major commuter route connecting Ann Arbor with the western suburbs of the Detroit metropolitan area.
-
B.
M-134
M-134 is a regional road in the Community of Madrid, Spain, that provides access to and from the town of Torrelaguna and connects it with nearby localities.
-
C.
M-13
M-13 is a state highway in Michigan that runs through the Saginaw Bay region, connecting communities such as Essexville with the broader state road network.
-
D.
M-45
M-45 is a state highway in Michigan that runs east–west through the Grand Rapids area toward the Lake Michigan shoreline.
-
E.
M-45
M-45 is a major ring road in the Madrid metropolitan area that helps divert traffic around the city and connect several eastern suburbs.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d85a06450081909c5a14ea9851a15e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e005b3f6f48190b1ed7c7b28feb7a6 |
completed | April 15, 2026, 9:40 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69febfea8e3081909551a8e3936c13a6 |
completed | May 9, 2026, 5:02 a.m. |
Created at: April 10, 2026, 3:07 a.m.