Triple
T19653154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quantrill's Raid |
E471865
|
entity |
| Predicate | civilianTargeted |
P16854
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Quantrill's Raid, civilianTargeted, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: civilianTargeted Context triple: [Quantrill's Raid, civilianTargeted, yes]
-
A.
civilianTarget
chosen
Indicates that the action or operation is directed at, affects, or designates civilians or civilian objects as the target.
-
B.
civilianImpact
Indicates the extent to which an action, event, or situation affects civilians, especially in terms of harm, disruption, or other consequences.
-
C.
civilian
Indicates that an entity is a non-military person or object associated with civilian status or context.
-
D.
casualtiesCiviliansKilled
Indicates that the relationship records the number of civilian deaths resulting from a specific event or action.
-
E.
perpetratorsTargeted
Indicates that the perpetrators intentionally selected or focused on specific targets for their actions.
- 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_69d8e51395348190ac1416d46dfc6db0 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e6414327d88190826ab9511f2f8e48 |
completed | April 20, 2026, 3:07 p.m. |
| PD | Predicate disambiguation | batch_69e514e941008190898d978d7bde91e4 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:44 p.m.