Triple
T32334587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hotchkiss machine gun |
E826137
|
entity |
| Predicate | variantCaliber |
P6076
|
FINISHED |
| Object | 7 mm Mauser |
—
|
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 mm Mauser | Statement: [Hotchkiss machine gun, variantCaliber, 7 mm Mauser]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: variantCaliber Context triple: [Hotchkiss machine gun, variantCaliber, 7 mm Mauser]
-
A.
caliberClass
Indicates a classification relationship where an entity is assigned to a specific caliber category based on its size or measurement.
-
B.
variant
Indicates that one entity is an alternative form, version, or variation of another entity.
-
C.
gunCalibre
chosen
Indicates the relationship between a firearm and the calibre (size/diameter) of ammunition it is designed to use.
-
D.
armedVariants
Indicates that one entity is a version or model of another that is equipped with weapons or enhanced armaments.
-
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_69f34913d9048190befaa634025232be |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6be1779cc8190abe386c03d31d385 |
completed | May 3, 2026, 3:16 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:48 a.m.