Triple
T17228931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | R. M. Hare |
E418193
|
entity |
| Predicate | placeOfDeath |
P21
|
FINISHED |
| Object | Ewelme |
E704097
|
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: Ewelme | Statement: [R. M. Hare, placeOfDeath, Ewelme]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ewelme Context triple: [R. M. Hare, placeOfDeath, Ewelme]
-
A.
Ewelme
chosen
Ewelme is a historic village in Oxfordshire, England, noted for its medieval church, almshouses, and picturesque rural setting.
-
B.
Umberleigh
Umberleigh is a small rural village in North Devon, England, situated on the River Taw and served by a local railway station.
-
C.
Wealdway
Wealdway is a long-distance walking route in southeast England that runs through the Weald, connecting the Thames Estuary to the English Channel.
-
D.
Elswick
Elswick is a district in Newcastle upon Tyne, England, historically known as a major industrial and shipbuilding center.
-
E.
Elswick
Elswick is a small rural village and civil parish in Lancashire, England, known for its countryside setting within the Borough of Fylde.
- 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_69d886d8e96081909870bff6c3d0bf09 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42df55e788190b442ffd4fac768c9 |
completed | April 19, 2026, 1:20 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a01675eae08819093427b4dc1ffee5f |
completed | May 11, 2026, 5:21 a.m. |
Created at: April 10, 2026, 5:39 a.m.