Triple
T14243020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M69 motorway |
E353058
|
entity |
| Predicate | roadNumber |
P1864
|
FINISHED |
| Object | M69 |
E1063375
|
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: M69 | Statement: [M69 motorway, roadNumber, M69]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: M69 Context triple: [M69 motorway, roadNumber, M69]
-
A.
M69
M69 is a dense globular star cluster located in the constellation Sagittarius and listed in Charles Messier’s catalog of deep-sky objects.
-
B.
M69
chosen
M69 is a motorway in England that connects the cities of Coventry and Leicester, serving as an important regional transport link in the Midlands.
-
C.
M67
M67 is an ancient, metal-rich open star cluster in the constellation Cancer, notable for its well-studied stellar population and importance in understanding stellar evolution.
-
D.
M67
M67 is a short motorway in Greater Manchester, England, connecting the M60 near Denton towards Hyde and intended as the first section of an unrealized trans-Pennine route.
-
E.
M59
M59 is an elliptical galaxy located in the constellation Virgo and is one of the prominent members of the Virgo Cluster.
- 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_69d8278adc7c8190a9218d69bce3c4e6 |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de6244ad188190b9d9db7914240410 |
completed | April 14, 2026, 3:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fd28235880819094f5983cce01b0fc |
completed | May 8, 2026, 12:02 a.m. |
Created at: April 10, 2026, 1:08 a.m.