Triple
T29114931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heckler & Koch MG5 |
E737018
|
entity |
| Predicate | standardChambering |
P177325
|
FINISHED |
| Object | 7.62×51mm 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: 7.62×51mm NATO | Statement: [Heckler & Koch MG5, standardChambering, 7.62×51mm NATO]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardChambering Context triple: [Heckler & Koch MG5, standardChambering, 7.62×51mm NATO]
-
A.
typicalLoadedChambers
Indicates that the number of loaded chambers in a firearm matches what is normally expected or standard for that type of weapon.
-
B.
hasChamber
Indicates that one entity possesses, contains, or is associated with a distinct enclosed space or compartment (a chamber).
-
C.
typicalEmptyChambers
Indicates that the subject typically has empty chambers or compartments as a characteristic state or condition.
-
D.
standardIssueMachineGun
Indicates that an entity is equipped with or uses the standard-issue machine gun designated for its organization, faction, or context.
-
E.
hasChamberSize
Indicates a relationship where an entity is associated with, or characterized by, a specific size of a chamber or internal compartment.
- F. None of above. chosen
Provenance (4 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_69f077ed54e08190bb02a744e8121a66 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6fb93224881908fc66fe76115fcdb |
completed | May 3, 2026, 7:38 a.m. |
| PD | Predicate disambiguation | batch_69f6f969b4cc8190afb473a2d8b110bc |
completed | May 3, 2026, 7:29 a.m. |
| PDg | Predicate description generation | batch_69f6fb17d5ec81909091e37e1ddbe577 |
completed | May 3, 2026, 7:36 a.m. |
Created at: April 28, 2026, 11:21 a.m.