Triple
T29745834
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | John I, Duke of Burgundy |
E752747
|
entity |
| Predicate | assassinatedOn |
P4179
|
FINISHED |
| Object | 1419-09-10 |
—
|
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: 1419-09-10 | Statement: [John I, Duke of Burgundy, assassinatedOn, 1419-09-10]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: assassinatedOn Context triple: [John I, Duke of Burgundy, assassinatedOn, 1419-09-10]
-
A.
assassinatedIn
Indicates that an assassination of one entity occurred within the specified location or context represented by another entity.
-
B.
wasAssassinatedIn
Indicates that an entity was killed in a deliberate, targeted assassination that occurred at a specific place or time.
-
C.
assassinationDate
chosen
Indicates the date on which an assassination of the referenced entity occurred.
-
D.
assassinated
Indicates that one entity deliberately killed another, typically for political, ideological, or strategic reasons.
-
E.
assassinationEvent
Indicates a deliberate killing of a specific individual, typically for political or strategic reasons, carried out as a planned event.
- 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_69f0d62b064081908c1ae61cd68fb139 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f67366211c8190b035057fa2665bf7 |
completed | May 2, 2026, 9:57 p.m. |
| PD | Predicate disambiguation | batch_69f66ac1a4fc81909740d2e52fbe6970 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 7:51 p.m.