Triple
T33666352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jagdpanzer IV early variants |
E862502
|
entity |
| Predicate | gunMuzzleBrake |
P177183
|
FINISHED |
| Object | initially equipped with muzzle brake |
—
|
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: initially equipped with muzzle brake | Statement: [Jagdpanzer IV early variants, gunMuzzleBrake, initially equipped with muzzle brake]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gunMuzzleBrake Context triple: [Jagdpanzer IV early variants, gunMuzzleBrake, initially equipped with muzzle brake]
-
A.
muzzleType
Indicates the specific style or configuration of a muzzle associated with an entity, such as a weapon or animal.
-
B.
hasMuzzle
Indicates that one entity possesses or is equipped with a muzzle, typically as a restraining or protective device.
-
C.
muzzleVelocity
Indicates the speed at which a projectile leaves the muzzle of a firearm or similar weapon at the moment it is fired.
-
D.
typeOfGunMount
Indicates the specific kind or configuration of gun mounting used to support or attach a gun.
-
E.
gunStabilisation
Indicates that an entity performs or provides stabilization for a gun, reducing its movement or recoil to improve accuracy.
- 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_69f34984c4008190bb82f33a7819da64 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fae2a7a8819099945d1706a94bfd |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f96dd4c8819093d6a7bd046a9ad5 |
completed | May 3, 2026, 7:29 a.m. |
| PDg | Predicate description generation | batch_69f6fa335b908190a20d92d5396203b5 |
completed | May 3, 2026, 7:33 a.m. |
Created at: May 1, 2026, 1:42 a.m.