Triple
T12695047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frank Debenham |
E303310
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Debenham |
E299719
|
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: Debenham | Statement: [Frank Debenham, familyName, Debenham]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Debenham Context triple: [Frank Debenham, familyName, Debenham]
-
A.
Debenham
chosen
Debenham is a historic village and civil parish in the Mid Suffolk district of Suffolk, England, known for its traditional architecture and rural character.
-
B.
Rendham
Rendham is a small rural village and civil parish located in the county of Suffolk in eastern England.
-
C.
Downham
Downham is a residential district in southeast London known for its interwar housing estates and suburban character within the London Borough of Lewisham.
-
D.
Downham
Downham is a picturesque rural village in Lancashire, England, known for its unspoiled traditional character and scenic setting near Pendle Hill.
-
E.
Denham
Denham is a surname of English origin borne by various notable individuals across fields such as politics, the arts, and sports.
- 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_69d7bdef90d48190b46b88270e780946 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d961ebd17081909f983567e4b36533 |
completed | April 10, 2026, 8:47 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f671ae935c8190a7fc2cf3c0987248 |
completed | May 2, 2026, 9:50 p.m. |
Created at: April 9, 2026, 5:22 p.m.