Triple
T19114534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rimfire Sporter Matches |
E467873
|
entity |
| Predicate | usesFirearmAction |
P66839
|
FINISHED |
| Object | magazine-fed rifle |
—
|
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: magazine-fed rifle | Statement: [Rimfire Sporter Matches, usesFirearmAction, magazine-fed rifle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesFirearmAction Context triple: [Rimfire Sporter Matches, usesFirearmAction, magazine-fed rifle]
-
A.
firearmActionType
chosen
Indicates the specific type or category of action performed with or by a firearm (such as firing, loading, carrying, or modifying).
-
B.
usesFirearmsUnit
Indicates that one entity employs or operates firearms as part of a specific unit or organizational grouping.
-
C.
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.
-
D.
gun
Indicates that one entity uses, carries, or is associated with a gun in relation to another entity or context.
-
E.
armed
Indicates that an entity is equipped with or carrying a weapon or weapons.
- 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_69d8dd06a26481908039e2a1bae8c597 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e39617408190b5134918f54f9c52 |
completed | April 20, 2026, 8:28 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b085288190b974d649e12e0844 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:05 p.m.