Triple
T13784238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | New Cross |
E331211
|
entity |
| Predicate | adjacentTo |
P224
|
FINISHED |
| Object | Peckham |
E164254
|
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: Peckham | Statement: [New Cross, adjacentTo, Peckham]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Peckham Context triple: [New Cross, adjacentTo, Peckham]
-
A.
Peckham
chosen
Peckham is a vibrant, multicultural district in south London known for its lively arts scene, markets, and diverse community.
-
B.
Brixton
Brixton is a vibrant district in south London known for its multicultural community, lively markets, music scene, and significant role in Black British culture.
-
C.
Rotherhithe
Rotherhithe is a historic riverside district in southeast London, known for its maritime heritage, docks, and long-standing connection to trade along the River Thames.
-
D.
Lewisham
Lewisham is a small inner-western suburb of Sydney, Australia, known for its residential character, heritage architecture, and convenient public transport links.
-
E.
Lewisham
Lewisham is a borough in southeast London known for its diverse communities, busy town centre, and extensive transport links into central London.
- 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_69d81c58feb08190a77bca8bf7d6d20f |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de0248db988190aa43c3723af25f90 |
completed | April 14, 2026, 9 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fec869957481909ea4fded01851b70 |
completed | May 9, 2026, 5:38 a.m. |
Created at: April 9, 2026, 10:11 p.m.