Triple
T4211529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M1 Garand |
E93911
|
entity |
| Predicate | chamberedVariant |
P9006
|
FINISHED |
| Object | 7.62×51mm NATO (converted versions) |
—
|
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 (converted versions) | Statement: [M1 Garand, chamberedVariant, 7.62×51mm NATO (converted versions)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chamberedVariant Context triple: [M1 Garand, chamberedVariant, 7.62×51mm NATO (converted versions)]
-
A.
chamberedFor
chosen
Indicates that a firearm is designed or configured to safely accept and fire a specific cartridge or ammunition type in its chamber.
-
B.
chamber1
Indicates that an entity is a chamber or room, typically serving as an enclosed space within a larger structure.
-
C.
chamber2
Indicates that one entity serves as a secondary or inner chamber, room, or compartment associated with another entity.
-
D.
chamberType
Indicates the specific kind or category of chamber associated with an entity (e.g., room, compartment, or enclosed space type).
-
E.
chamberSupportedBy
Indicates that a chamber is physically held up, carried, or structurally sustained by another object or structure.
- 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_69b3451743608190808f41d17ccf2650 |
completed | March 12, 2026, 10:58 p.m. |
| NER | Named-entity recognition | batch_69b34e098da881909a0cc339cc186627 |
completed | March 12, 2026, 11:36 p.m. |
| PD | Predicate disambiguation | batch_69b347efd9b08190bb50f82e4e7fe06d |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:04 p.m.