Triple
T13335067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UB postcode area |
E317666
|
entity |
| Predicate | containsTown |
P847
|
FINISHED |
| Object | Denham |
E212056
|
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: Denham | Statement: [UB postcode area, containsTown, Denham]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Denham Context triple: [UB postcode area, containsTown, Denham]
-
A.
Denham
chosen
Denham is a village in Buckinghamshire, England, known for its historic charm, green spaces, and proximity to both the countryside and Greater London.
-
B.
Denham
Denham is a small coastal town in Western Australia that serves as the main settlement and tourist gateway to the Shark Bay World Heritage Area.
-
C.
Denham
Denham is a surname of English origin borne by various notable individuals across fields such as politics, the arts, and sports.
-
D.
Turnford
Turnford is a village and residential area in the Broxbourne district of Hertfordshire, England, forming part of the London commuter belt.
-
E.
Debenham
Debenham is a historic village and civil parish in the Mid Suffolk district of Suffolk, England, known for its traditional architecture and rural 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_69d806b5a3c08190b42c267fb092f98a |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d99cff44e08190b9583baf0b626e42 |
completed | April 11, 2026, 12:59 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7267132488190a62930e98be70640 |
completed | May 3, 2026, 10:41 a.m. |
Created at: April 9, 2026, 9:30 p.m.