Triple
T22628163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kalashnikov rifle family |
E558478
|
entity |
| Predicate | hasMagazineCapacityVariant |
P25151
|
FINISHED |
| Object | 40-round magazine |
—
|
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: 40-round magazine | Statement: [Kalashnikov rifle family, hasMagazineCapacityVariant, 40-round magazine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMagazineCapacityVariant Context triple: [Kalashnikov rifle family, hasMagazineCapacityVariant, 40-round magazine]
-
A.
hasMagazineType
Indicates that an entity is associated with, or classified by, a specific type or category of magazine.
-
B.
hasChamberSize
Indicates a relationship where an entity is associated with, or characterized by, a specific size of a chamber or internal compartment.
-
C.
ammunitionCapacity
chosen
Indicates the maximum amount of ammunition that something (typically a weapon or container) is designed to hold at one time.
-
D.
hasChamber
Indicates that one entity possesses, contains, or is associated with a distinct enclosed space or compartment (a chamber).
-
E.
hasChamberSelectionMethod
Indicates the method or process by which a particular chamber is chosen, designated, or determined.
- 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_69e245467d9881908d6985bd0db7a1f1 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f16e3ed1d48190a093013d829901b9 |
completed | April 29, 2026, 2:34 a.m. |
| PD | Predicate disambiguation | batch_69ee62855558819080da946c7b35a160 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 17, 2026, 3:02 p.m.