Triple
T14133672
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R. A. Butler |
E350232
|
entity |
| Predicate | placeOfDeath |
P21
|
FINISHED |
| Object | Great Yeldham |
E1069770
|
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: Great Yeldham | Statement: [R. A. Butler, placeOfDeath, Great Yeldham]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Great Yeldham Context triple: [R. A. Butler, placeOfDeath, Great Yeldham]
-
A.
Great Yeldham
chosen
Great Yeldham is a village and civil parish in the Braintree district of Essex, England.
-
B.
Teynham
Teynham is a village and civil parish in the Swale district of Kent, England, known historically for its fruit-growing and hop-growing agriculture.
-
C.
Wivenhoe
Wivenhoe is a locality in Queensland, Australia, situated near the Wivenhoe Dam and associated with the broader Sunshine Coast region.
-
D.
Wivenhoe
Wivenhoe is a riverside town in Essex, England, known for its historic maritime character, artistic community, and proximity to the University of Essex.
-
E.
Henham
Henham is a small rural village located in the English county of Suffolk.
- 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_69d827865f608190b311820428ae027b |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de610e949c8190852d336c9d12bfd0 |
completed | April 14, 2026, 3:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fcdf1288b48190a382732fac13aaf7 |
completed | May 7, 2026, 6:50 p.m. |
Created at: April 9, 2026, 11:40 p.m.