Triple
T18290538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beslan |
E438099
|
entity |
| Predicate | schoolSiegeVictimsIncluded |
P130530
|
FINISHED |
| Object | many children |
—
|
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: many children | Statement: [Beslan, schoolSiegeVictimsIncluded, many children]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: schoolSiegeVictimsIncluded Context triple: [Beslan, schoolSiegeVictimsIncluded, many children]
-
A.
numberOfChildVictims
chosen
Indicates the count of individuals who are victims and are classified as children in the context of the described event or situation.
-
B.
hasVictims
Indicates that an entity has one or more individuals who have been harmed, injured, or adversely affected by it.
-
C.
numberOfSuspectedVictims
Indicates the count of individuals believed or alleged to be victims in a particular incident, case, or context.
-
D.
mainVictims
Indicates that the related entities are the primary or principal targets harmed or affected by an action, event, or perpetrator.
-
E.
numberOfVictimsClaimed
Indicates the reported count of victims associated with a particular event, incident, or action.
- 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_69d8b914530c8190b4474d862a2b2a1b |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e500fee5248190928e68ddaa4d90d7 |
completed | April 19, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69e44fdf43d08190bbcfb6b1fe3cc0ee |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:35 a.m.