Triple
T8348944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M20 |
E196109
|
entity |
| Predicate | hasJunction |
P1018
|
FINISHED |
| Object | Junction 4 |
E728755
|
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: Junction 4 | Statement: [M20, hasJunction, Junction 4]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Junction 4 Context triple: [M20, hasJunction, Junction 4]
-
A.
Junction 6
Junction 6 is an interchange on England’s M58 motorway connecting local roads to the regional motorway network.
-
B.
Junction 7
Junction 7 is a numbered junction on England’s M58 motorway, serving as one of the route’s access and exit points.
-
C.
Junction 1
Junction 1 is a major road interchange on England’s M58 motorway, connecting it with local and regional routes.
-
D.
Junction 1
chosen
Junction 1 is a motorway interchange on the M20 in southeast England, providing access between the M20 and local roads near the London orbital route.
-
E.
Junction 3
Junction 3 is a numbered exit on England’s M66 motorway serving local connections in the Greater Manchester area.
- 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_69ca82edd63c8190b876b8465464c5fa |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb8016c4188190a5ff93078e74dc39 |
completed | March 31, 2026, 8:04 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cde7b2d00c8190b7df13a0853a6374 |
completed | April 2, 2026, 3:51 a.m. |
Created at: March 30, 2026, 5:58 p.m.