Triple
T19396655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wood Green |
E485206
|
entity |
| Predicate | borough |
P300
|
FINISHED |
| Object | Haringey |
E614139
|
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: Haringey | Statement: [Wood Green, borough, Haringey]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Haringey Context triple: [Wood Green, borough, Haringey]
-
A.
Haringey
chosen
Haringey is a London borough in north London that includes areas such as Tottenham, Wood Green, and Muswell Hill.
-
B.
Redbridge
Redbridge is a borough in northeast London, England, known for its suburban character, green spaces, and diverse communities.
-
C.
Newham
Newham is a diverse, densely populated borough in East London known for its major regeneration projects, including the Queen Elizabeth Olympic Park and surrounding developments.
-
D.
Barnet
Barnet is a suburban area and parliamentary constituency in North London, England, known for its residential character and role in Greater London politics.
-
E.
Enfield and Haringey
Enfield and Haringey is a London Assembly constituency in North London that elects a representative to the Greater London Authority.
- 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_69d8e8d5162481909db12435d9535c1a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e62573f5788190a635b92121db2cf7 |
completed | April 20, 2026, 1:09 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a07bd4c2de48190843b04b1a1eeaa8f |
completed | May 16, 2026, 12:41 a.m. |
Created at: April 10, 2026, 1:36 p.m.