Triple
T12347726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Garston Docks |
E294400
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | A561 road |
—
|
NE NERFINISHED |
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: A561 road | Statement: [Garston Docks, locatedNear, A561 road]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: A561 road Context triple: [Garston Docks, locatedNear, A561 road]
-
A.
A561 road
chosen
The A561 road is a major route in Merseyside, England, running between Liverpool and Widnes and serving as a key link through suburbs such as Halewood.
-
B.
A56 road
The A56 road is a major route in North West England connecting Chester to the Manchester area and beyond, serving as an important link between urban centers and the motorway network.
-
C.
A565 road
The A565 road is a major route in North West England that connects Liverpool with Southport and other nearby towns, serving as an important commuter and regional traffic corridor.
-
D.
A560 road
The A560 road is a significant route in Greater Manchester, England, connecting various suburbs and facilitating regional traffic flow.
-
E.
A562 road
The A562 road is a major route in Merseyside, England, linking Liverpool with surrounding areas including Halewood and Widnes.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d6ab6ccbec8190b09e2d357aa80064 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f7ba17481908b03af7316b28d9b |
completed | April 10, 2026, 6:20 p.m. |
Created at: April 8, 2026, 9:53 p.m.