Triple
T1619059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lymm |
E34787
|
entity |
| Predicate | nearbyMotorway |
P25934
|
FINISHED |
| Object | M62 |
E82189
|
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: M62 | Statement: [Lymm, nearbyMotorway, M62]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: M62 Context triple: [Lymm, nearbyMotorway, M62]
-
A.
M62
chosen
M62 is a major trans-Pennine motorway in northern England connecting cities such as Liverpool, Manchester, Leeds, and Hull.
-
B.
M60
M60 is a major orbital motorway encircling the city of Manchester in Greater Manchester, England.
-
C.
M-72
M-72 is a state highway in northern Michigan that serves as a key east–west route connecting Traverse City with several inland communities and recreational areas.
-
D.
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.
-
E.
M-45
M-45 is a state highway in Michigan that runs east–west through the Grand Rapids area toward the Lake Michigan shoreline.
- 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_69a885ffc5ec819091afa325d5f9611c |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aa61df32a88190a7e823a77bdcc84a |
completed | March 6, 2026, 5:10 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad51cf7b7c8190847ab6795fb5613b |
completed | March 8, 2026, 10:39 a.m. |
Created at: March 4, 2026, 7:28 p.m.