Triple
T17169186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moscow theater hostage crisis |
E416683
|
entity |
| Predicate | attackerFatalities |
P67514
|
FINISHED |
| Object | all or nearly all attackers killed |
—
|
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: all or nearly all attackers killed | Statement: [Moscow theater hostage crisis, attackerFatalities, all or nearly all attackers killed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: attackerFatalities Context triple: [Moscow theater hostage crisis, attackerFatalities, all or nearly all attackers killed]
-
A.
casualtiesAttackersKilled
chosen
Indicates the number of attacking forces who were killed as a result of the attack.
-
B.
numberOfVictimsKilled
Indicates the count of victims who were killed as a result of the referenced event or action.
-
C.
numberOfPerpetratorsKilled
Indicates the count of perpetrators who were killed in the context of the described event or incident.
-
D.
numberOfVictimsClaimed
Indicates the reported count of victims associated with a particular event, incident, or action.
-
E.
numberOfHostagesKilled
Indicates the number of hostages who were killed in the context of a specific event or situation.
- 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_69d886d5f34c8190b24564dfaa63f3fb |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f9173ee48190bc46622c78479603 |
completed | April 18, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69e3830d2a90819092386717dc56f0e8 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:37 a.m.