Triple
T4117363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waco siege |
E90324
|
entity |
| Predicate | reasonForRaid |
P54359
|
FINISHED |
| Object | suspected federal firearms violations |
—
|
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: suspected federal firearms violations | Statement: [Waco siege, reasonForRaid, suspected federal firearms violations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reasonForRaid Context triple: [Waco siege, reasonForRaid, suspected federal firearms violations]
-
A.
raidedRegion
Indicates that an agent carried out a raid targeting or occurring within a specified region.
-
B.
reasonForScuttling
Indicates the specific cause or motivation that led to a vessel being deliberately scuttled.
-
C.
reasonForBan
Indicates the justification or cause that led to an entity being banned.
-
D.
reasonForLocation
Indicates the cause, purpose, or justification for why an entity is at a particular location.
-
E.
reasonForRelocation
Indicates the underlying cause, motivation, or circumstance that led an entity to move from one location to another.
- 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_69aed95c080881908125e30c5dcdc6f8 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af0246e40081908ad6741a830ca68e |
completed | March 9, 2026, 5:24 p.m. |
| PD | Predicate disambiguation | batch_69af01867698819098e4144634b2ec4f |
completed | March 9, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69af0245adbc81908b89a40850047975 |
completed | March 9, 2026, 5:24 p.m. |
Created at: March 9, 2026, 3:41 p.m.