Triple
T5158849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A406 road |
E116382
|
entity |
| Predicate | passesNear |
P416
|
FINISHED |
| Object | Brent Cross |
E404949
|
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: Brent Cross | Statement: [A406 road, passesNear, Brent Cross]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Brent Cross Context triple: [A406 road, passesNear, Brent Cross]
-
A.
Brent Cross
chosen
Brent Cross is a district in northwest London best known for its large shopping centre and major road junction.
-
B.
Hunts Cross
Hunts Cross is a suburban residential area in south Liverpool, England, known for its railway station and proximity to Liverpool John Lennon Airport.
-
C.
Turners Cross
Turners Cross is a residential suburb of Cork City, Ireland, known for its football stadium and local community amenities.
-
D.
Waltham Cross
Waltham Cross is a town in southeastern England known for its historic Eleanor Cross and its location near the Greater London boundary.
-
E.
Leyland Cross
Leyland Cross is a historic stone market cross and local landmark located in the town of Leyland, Lancashire, England.
- 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_69bd445edb3881909b93b34d260717fc |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7904457c819090f382029ebb2b43 |
completed | March 20, 2026, 4:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bed01a85f88190827a79a2c26e539f |
completed | March 21, 2026, 5:06 p.m. |
Created at: March 20, 2026, 1:44 p.m.