Triple
T17274254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beslan school siege |
E419343
|
entity |
| Predicate | numberOfChildrenTakenHostage |
P36180
|
FINISHED |
| Object | over 700 |
—
|
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: over 700 | Statement: [Beslan school siege, numberOfChildrenTakenHostage, over 700]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfChildrenTakenHostage Context triple: [Beslan school siege, numberOfChildrenTakenHostage, over 700]
-
A.
numberOfHostages
chosen
Indicates the quantity of hostages involved in a particular situation, event, or context.
-
B.
numberOfHostagesKilled
Indicates the number of hostages who were killed in the context of a specific event or situation.
-
C.
hostages
Indicates that one party is forcibly holding another party captive, typically to compel a third party to meet certain demands or conditions.
-
D.
takesHostageDuring
Indicates that one entity seizes and holds another entity as a hostage in the course of a particular event or action.
-
E.
grantedHostages
Indicates that one party has given or handed over hostages to another party, typically as a guarantee or security in an agreement or conflict.
- 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_69d886da626481908a14ce7830329a35 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42f4c209c81909c713ed78f2cb19a |
completed | April 19, 2026, 1:26 a.m. |
| PD | Predicate disambiguation | batch_69e3832c3b98819091967ac7e91ba316 |
completed | April 18, 2026, 1:12 p.m. |
Created at: April 10, 2026, 5:40 a.m.