Triple
T15817511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M242 Bushmaster |
E383516
|
entity |
| Predicate | weaponAction |
P66839
|
FINISHED |
| Object | chain-driven |
—
|
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: chain-driven | Statement: [M242 Bushmaster, weaponAction, chain-driven]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: weaponAction Context triple: [M242 Bushmaster, weaponAction, chain-driven]
-
A.
weaponControl
Indicates that one entity has authority over, access to, or the ability to direct the use of a weapon associated with another entity.
-
B.
firearmActionType
chosen
Indicates the specific type or category of action performed with or by a firearm (such as firing, loading, carrying, or modifying).
-
C.
weapon
Indicates that one entity is used as a weapon by, or serves as the weapon of, another entity.
-
D.
weaponsUsed
Indicates that one entity employed or utilized another entity as a weapon in carrying out an action or event.
-
E.
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.
- 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_69d86da2858c819090cc8481e7207b6e |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e0c4a4332c8190bc525e06d6f3a6b4 |
completed | April 16, 2026, 11:14 a.m. |
| PD | Predicate disambiguation | batch_69e0053b847c8190945726c3ddac21cc |
completed | April 15, 2026, 9:38 p.m. |
Created at: April 10, 2026, 4:49 a.m.