Triple
T14471670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greenham Common |
E358857
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | A339 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: A339 road | Statement: [Greenham Common, locatedNear, A339 road]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: A339 road Context triple: [Greenham Common, locatedNear, A339 road]
-
A.
A339 road
chosen
The A339 road is a primary route in southern England that connects Newbury in Berkshire with Basingstoke in Hampshire.
-
B.
A337 road
The A337 road is a primary route in southern England that runs through the New Forest area, connecting towns such as Lymington and Lyndhurst.
-
C.
A329 road
The A329 road is a major route in England that runs through Oxfordshire and Berkshire, linking towns such as Thame, Reading, and Bracknell.
-
D.
A349 road
The A349 road is a primary route in Dorset, England, connecting Poole with nearby towns and serving as a key local transport corridor.
-
E.
A39 road
The A39 road is a major route in southwest England running along much of the north coast of Cornwall and Devon, linking several coastal towns and connecting with key trunk roads.
- 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_69d827966698819082e140837737501d |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de91fab21c819090b6e209d8efba6e |
completed | April 14, 2026, 7:14 p.m. |
Created at: April 10, 2026, 1:20 a.m.