Triple
T12335038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oxford, Michigan |
E294061
|
entity |
| Predicate | roadAccessVia |
P9041
|
FINISHED |
| Object | M-24 |
E395607
|
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-24 | Statement: [Oxford, Michigan, roadAccessVia, M-24]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: M-24 Context triple: [Oxford, Michigan, roadAccessVia, M-24]
-
A.
M-24
chosen
M-24 is a state highway in Michigan that serves as a key north–south transportation route through communities such as Orion Township.
-
B.
M24
M24 is a rich star cloud in the constellation Sagittarius, visible as a bright patch of the Milky Way and often observed by amateur astronomers.
-
C.
M-20
M-20 is a state trunkline highway in Michigan that runs east–west across the central part of the state, connecting communities such as Midland to the broader regional road network.
-
D.
M-52
M-52 is a state highway in Michigan that runs north–south through several counties, serving as an important regional route for local and through traffic.
-
E.
M-28
M-28 is a major east–west state highway running across Michigan’s Upper Peninsula, connecting numerous communities along the southern shore of Lake Superior.
- 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_69d6ab6ae0dc8190b1522a9c1c55c114 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f6683e881908920e1fee02a14e3 |
completed | April 10, 2026, 6:20 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f62aa367348190b3991f256586a331 |
completed | May 2, 2026, 4:47 p.m. |
Created at: April 8, 2026, 9:53 p.m.