Triple
T8721809
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FAMAS F1 |
E207028
|
entity |
| Predicate | originalCaliberSpecification |
P6076
|
FINISHED |
| Object | 5.56×45mm M193 |
—
|
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 M193 | Statement: [FAMAS F1, originalCaliberSpecification, 5.56×45mm M193]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalCaliberSpecification Context triple: [FAMAS F1, originalCaliberSpecification, 5.56×45mm M193]
-
A.
gunCalibre
chosen
Indicates the relationship between a firearm and the calibre (size/diameter) of ammunition it is designed to use.
-
B.
natoCaliberClass
Indicates that two ammunition types share the same standardized NATO caliber classification.
-
C.
barrelLengthInCalibers
Indicates the length of a barrel expressed as a multiple of its bore diameter (in calibers), describing how many times the bore diameter fits into the barrel length.
-
D.
supportsCaliber
Indicates that one entity is compatible with and able to accommodate or function with a specified caliber.
-
E.
successorCaliber
Indicates that one entity serves as the successor or follow-up version in terms of quality, standard, or specification relative to another.
- 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_69ca835811d8819081ea00fd2a2c9a1c |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5d03f0848190a50c77e5cd028ee7 |
completed | March 31, 2026, 11:47 p.m. |
| PD | Predicate disambiguation | batch_69cc457093188190959287a6458651c6 |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:36 p.m.