Triple
T22628156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kalashnikov rifle family |
E558478
|
entity |
| Predicate | hasCaliberVariant |
P6076
|
FINISHED |
| Object | 7.62×39mm |
—
|
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: 7.62×39mm | Statement: [Kalashnikov rifle family, hasCaliberVariant, 7.62×39mm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCaliberVariant Context triple: [Kalashnikov rifle family, hasCaliberVariant, 7.62×39mm]
-
A.
supportsCaliber
Indicates that one entity is compatible with and able to accommodate or function with a specified caliber.
-
B.
hasChamberSize
Indicates a relationship where an entity is associated with, or characterized by, a specific size of a chamber or internal compartment.
-
C.
hasArtilleryCaliber
Indicates that an artillery piece is characterized by or equipped with a specific caliber (diameter) of its gun barrel or ammunition.
-
D.
gunCalibre
chosen
Indicates the relationship between a firearm and the calibre (size/diameter) of ammunition it is designed to use.
-
E.
hasHeavierBarrelThan
Indicates that the barrel of one entity has a greater weight than the barrel of another 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_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.