Triple
T6036182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Culcheth |
E134426
|
entity |
| Predicate | hasNearbyMotorway |
P385
|
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: [Culcheth, hasNearbyMotorway, M62]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: M62 Context triple: [Culcheth, hasNearbyMotorway, 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.
M60
M60 is a massive elliptical galaxy in the constellation Virgo, notable as one of the brightest and largest members of the Virgo Cluster.
-
D.
M61
M61 is a major motorway in North West England connecting Manchester with Preston and linking into the wider UK motorway network.
-
E.
M26
The M26 is a U.S. World War II–era heavy/medium tank, commonly known as the M26 Pershing, that served as a precursor to the American Patton tank series.
- 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_69c00875db5c819099dd5bb833ec43c2 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c056b4e3ec819089b2d119ea2953fe |
completed | March 22, 2026, 8:53 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c1138cb2388190a80562a835388dc3 |
completed | March 23, 2026, 10:18 a.m. |
Created at: March 22, 2026, 4:08 p.m.