Triple
T34876797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Loyada school bus hostage rescue |
E1005900
|
entity |
| Predicate | weaponUsedByPerpetrators |
P820
|
FINISHED |
| Object | firearms |
—
|
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: firearms | Statement: [Loyada school bus hostage rescue, weaponUsedByPerpetrators, firearms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: weaponUsedByPerpetrators Context triple: [Loyada school bus hostage rescue, weaponUsedByPerpetrators, firearms]
-
A.
weaponUsedIn
Indicates that a particular weapon is employed or involved in carrying out a specific event or action.
-
B.
weaponUsedAgainst
Indicates that a particular weapon or instrument is employed in an act of aggression, attack, or harm directed toward a specific target or entity.
-
C.
weaponsUsed
chosen
Indicates that one entity employed or utilized another entity as a weapon in carrying out an action or event.
-
D.
weaponDepicted
Indicates that a weapon is visually represented or shown in association with an entity.
-
E.
weaponsRepresent
Indicates that certain weapons serve as symbols or embodiments of something, such as ideas, groups, or values.
- 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_69f76dbde1c08190a24e7f9beb564c8d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78710282c81909146dc0be91e983f |
completed | May 3, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f784162134819098413482ef52042f |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4 p.m.