Triple
T29749743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FAMAS family |
E752861
|
entity |
| Predicate | hasPrimaryCaliber |
P6076
|
FINISHED |
| Object | 5.56×45mm NATO |
—
|
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: 5.56×45mm NATO | Statement: [FAMAS family, hasPrimaryCaliber, 5.56×45mm NATO]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPrimaryCaliber Context triple: [FAMAS family, hasPrimaryCaliber, 5.56×45mm NATO]
-
A.
isLargerCaliberCounterpartOf
Indicates that one item is the higher-caliber version or counterpart of another, typically within the same general type or family of objects.
-
B.
gunCalibre
chosen
Indicates the relationship between a firearm and the calibre (size/diameter) of ammunition it is designed to use.
-
C.
caliberClass
Indicates a classification relationship where an entity is assigned to a specific caliber category based on its size or measurement.
-
D.
hasHeavierBarrelThan
Indicates that the barrel of one entity has a greater weight than the barrel of another entity.
-
E.
hasArtilleryCaliber
Indicates that an artillery piece is characterized by or equipped with a specific caliber (diameter) of its gun barrel or ammunition.
- 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_69f0d62c84cc8190846f80ae04fdf8ec |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69ff9b1ad27081908f8a492396950795 |
completed | May 9, 2026, 8:37 p.m. |
| PD | Predicate disambiguation | batch_69ff9a6354c48190ae21070c1424cb7a |
completed | May 9, 2026, 8:34 p.m. |
Created at: April 28, 2026, 7:53 p.m.