Triple
T22959557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Holloway Road area |
E570854
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Highbury |
—
|
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: Highbury | Statement: [Holloway Road area, near, Highbury]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Highbury Context triple: [Holloway Road area, near, Highbury]
-
A.
Highbury
Highbury was Arsenal Football Club’s historic North London stadium, renowned for its Art Deco design and intimate atmosphere before the club’s move to the Emirates Stadium.
-
B.
Highbury
Highbury is a residential suburb located within the city of Palmerston North in New Zealand.
-
C.
Highbury
Highbury is the fictional English village that serves as the primary setting of Jane Austen’s novel "Emma."
-
D.
Highbury
chosen
Highbury is a district in North London, England, known historically as a middle-class residential area and for being the former home of Arsenal Football Club’s stadium.
-
E.
Highbury Corner
Highbury Corner is a busy road junction and public space in the Highbury district of north London, near the Highbury & Islington transport hub.
- 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_69e245b212a88190b5259caf51606084 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f181f3c96081909abd6ec32103d4c3 |
completed | April 29, 2026, 3:58 a.m. |
Created at: April 17, 2026, 3:47 p.m.