Triple
T26827217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John Hicks |
E675404
|
entity |
| Predicate | placeOfInterment |
P196
|
FINISHED |
| Object | Wolvercote Cemetery |
—
|
NE NERFINISHED |
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: Wolvercote Cemetery | Statement: [John Hicks, placeOfInterment, Wolvercote Cemetery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placeOfInterment Context triple: [John Hicks, placeOfInterment, Wolvercote Cemetery]
-
A.
burialPlace
chosen
Indicates the location where a person or entity is buried.
-
B.
associatedCemetery
Indicates that there is a relationship linking an entity (such as a person, event, or organization) to a specific cemetery with which it is connected.
-
C.
locatedInCemetery
Indicates that one entity is situated within the grounds or area of a cemetery.
-
D.
reputedBurialPlaceOf
Indicates a location that is widely believed or traditionally thought to be the burial place of a particular person or group.
-
E.
cremationPlace
Indicates the place where a person or entity was cremated.
- F. None of above.
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_69eee9b6b28481909332f83eb17e5170 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 27, 2026, 4:59 a.m.