Triple
T21318241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Newham |
E525534
|
entity |
| Predicate | borderedBy |
P224
|
FINISHED |
| Object | Redbridge |
—
|
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: Redbridge | Statement: [Newham, borderedBy, Redbridge]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Redbridge Context triple: [Newham, borderedBy, Redbridge]
-
A.
Redbridge
chosen
Redbridge is a borough in northeast London, England, known for its suburban character, green spaces, and diverse communities.
-
B.
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.
-
C.
Lewisham
Lewisham is a small inner-western suburb of Sydney, Australia, known for its residential character, heritage architecture, and convenient public transport links.
-
D.
Lewisham
Lewisham is a borough in southeast London known for its diverse communities, busy town centre, and extensive transport links into central London.
-
E.
Islington
Islington is a vibrant inner London borough in England known for its dense urban character, cultural venues, and strong football heritage.
- 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_69e0b51ad810819098c12392c8e55f6c |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e77ece1c348190aaa9c52474b57b2f |
completed | April 21, 2026, 1:42 p.m. |
Created at: April 16, 2026, 4:37 p.m.