Triple
T36835598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Henschel turret for Tiger II |
E910262
|
entity |
| Predicate | coaxialArmament |
P6067
|
FINISHED |
| Object | 7.92 mm MG34 machine gun |
—
|
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.92 mm MG34 machine gun | Statement: [Henschel turret for Tiger II, coaxialArmament, 7.92 mm MG34 machine gun]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coaxialArmament Context triple: [Henschel turret for Tiger II, coaxialArmament, 7.92 mm MG34 machine gun]
-
A.
aircraftArmament
Indicates that an aircraft is equipped with a particular weapon or armament system.
-
B.
primaryArmament
Indicates the main weapon or principal offensive system that an entity (such as a vehicle, vessel, or platform) is equipped with or uses.
-
C.
rocketArmament
Indicates that an entity is equipped with or carries rocket-based weaponry as part of its armament.
-
D.
secondaryArmament
chosen
Indicates that one entity serves as a secondary or auxiliary weapon system associated with another primary platform or armament.
-
E.
aircraftDefensiveArmament
Indicates that an aircraft is equipped with weapons or systems specifically intended for its own defense against attacks.
- 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_69f76e7e9d60819092442fba73290a46 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fd6834cc8190aa27153d6a99f3bb |
completed | May 5, 2026, 2:23 p.m. |
| PD | Predicate disambiguation | batch_69f7cf7890008190a8bc355ff2d61c86 |
completed | May 3, 2026, 10:43 p.m. |
Created at: May 3, 2026, 4:13 p.m.