Triple
T1971897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Martin Bucer |
E42818
|
entity |
| Predicate | posthumousEvent |
P4225
|
FINISHED |
| Object | body exhumed and burned in 1557 under Queen Mary I |
—
|
LITERAL 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: body exhumed and burned in 1557 under Queen Mary I | Statement: [Martin Bucer, posthumousEvent, body exhumed and burned in 1557 under Queen Mary I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: posthumousEvent Context triple: [Martin Bucer, posthumousEvent, body exhumed and burned in 1557 under Queen Mary I]
-
A.
isPosthumous
chosen
Indicates that something occurs, is created, or is conferred after the death of the person to whom it relates.
-
B.
posthumousReputation
Indicates the reputation or standing attributed to a person after their death.
-
C.
deathDateEvent
Indicates the date on which a death occurred or a death-related event took place.
-
D.
notableDeath
Indicates that an entity’s death is considered significant or noteworthy in some context.
-
E.
endedActivityAfterDeathOf
Indicates that an activity was terminated following, and as a consequence of, the death of a specified entity.
- 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_69a8871289048190b00b0d7744b7b2b1 |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abb3f275408190affa93f8cb6a8184 |
completed | March 7, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69abaff7d4a48190ab0d51aefb1c4e31 |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:36 p.m.