Triple
T13596487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cockfosters |
E324834
|
entity |
| Predicate | near |
P350
|
FINISHED |
| Object | Southgate |
E394186
|
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: Southgate | Statement: [Cockfosters, near, Southgate]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Southgate Context triple: [Cockfosters, near, Southgate]
-
A.
Southgate
Southgate is a coastal village on Wales’s scenic Gower Peninsula, known for its dramatic cliffs, beaches, and walking paths.
-
B.
Southgate
Southgate is a residential neighbourhood and ward within the town of Crawley in West Sussex, England.
-
C.
Southgate, London
chosen
Southgate, London is a suburban area in the London Borough of Enfield known for its residential character, green spaces, and historic links to notable literary figures.
-
D.
Derby
Derby is a small coastal town in Western Australia's Kimberley region, known as a gateway to the outback and for its large tidal variations and proximity to the Buccaneer Archipelago.
-
E.
Derby
Derby is a neighborhood within the Brazilian city of Recife, known for its central location and urban character.
- 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_69d80769eaf081909d82f44e484d6113 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb0590558819080ccc5874a650b1e |
completed | April 12, 2026, 2:46 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f76bc99dac8190bc267fdf405e8d58 |
completed | May 3, 2026, 3:37 p.m. |
Created at: April 9, 2026, 9:49 p.m.