Triple
T17119643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Branch Davidians |
E415430
|
entity |
| Predicate | notableDeathTollEvent |
P126019
|
FINISHED |
| Object | 1993 Waco siege |
—
|
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: 1993 Waco siege | Statement: [Branch Davidians, notableDeathTollEvent, 1993 Waco siege]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableDeathTollEvent Context triple: [Branch Davidians, notableDeathTollEvent, 1993 Waco siege]
-
A.
deathToll
Indicates the number of deaths resulting from a particular event, situation, or cause.
-
B.
notableDeath
Indicates that an entity’s death is considered significant or noteworthy in some context.
-
C.
deathTollEstimate
Indicates an estimated number of deaths attributed to a particular event, cause, or period.
-
D.
notableVictims
Indicates that the object is a person or group who is especially well-known or significant as a victim of the subject.
-
E.
casualtiesAssociatedWithEvent
Indicates that certain casualties (deaths or injuries) are linked to, or resulted from, a specific event.
- F. None of above. chosen
Provenance (4 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_69d886d090cc8190a39cb94992586905 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3e8092b548190b45c1695be47edc2 |
completed | April 18, 2026, 8:22 p.m. |
| PD | Predicate disambiguation | batch_69e35d6b1b988190a8d6b6fe78c35e59 |
completed | April 18, 2026, 10:31 a.m. |
| PDg | Predicate description generation | batch_69e37542d060819082aa73948eb8ebd4 |
completed | April 18, 2026, 12:12 p.m. |
Created at: April 10, 2026, 5:36 a.m.