Triple
T28310935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Noveske Rifleworks |
E713989
|
entity |
| Predicate | firearmPlatform |
P6073
|
FINISHED |
| Object | semi-automatic rifles |
—
|
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: semi-automatic rifles | Statement: [Noveske Rifleworks, firearmPlatform, semi-automatic rifles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firearmPlatform Context triple: [Noveske Rifleworks, firearmPlatform, semi-automatic rifles]
-
A.
gunType
chosen
Indicates the specific category or kind of gun associated with an entity.
-
B.
lightArmament
Indicates that an entity is equipped with or characterized by relatively minimal or lightweight weaponry compared to standard or heavy armament.
-
C.
firearmActionType
Indicates the specific type or category of action performed with or by a firearm (such as firing, loading, carrying, or modifying).
-
D.
isServiceRifleOf
Indicates that one entity is the designated service rifle used by another entity, typically a military or armed force.
-
E.
gun
Indicates that one entity uses, carries, or is associated with a gun in relation to another entity or context.
- 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_69efb5256afc8190b9322d25c3ae6320 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f644e1e0b48190b48f3e7b5d408dbd |
completed | May 2, 2026, 6:39 p.m. |
| PD | Predicate disambiguation | batch_69f641e0fde08190bf06a1c5b388aa84 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 27, 2026, 11:40 p.m.