Triple
T8587998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PzH 2000 |
E203355
|
entity |
| Predicate | burstFireCapability |
P17731
|
FINISHED |
| Object | 3 rounds in 9 seconds |
—
|
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: 3 rounds in 9 seconds | Statement: [PzH 2000, burstFireCapability, 3 rounds in 9 seconds]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: burstFireCapability Context triple: [PzH 2000, burstFireCapability, 3 rounds in 9 seconds]
-
A.
burnCapability
Indicates that an entity has the ability or potential to burn, ignite, or cause combustion under certain conditions.
-
B.
rateOfFire
chosen
Indicates the frequency at which a weapon or system can discharge projectiles or shots over a given period of time.
-
C.
fireModes
Indicates the different ways or settings in which a weapon or device can be fired or operated.
-
D.
fireEffect
Indicates that one entity produces, causes, or is associated with a fire-related impact or consequence on another entity.
-
E.
firingCharacteristic
Indicates the specific way in which an entity initiates or sustains firing or discharge, such as its pattern, mode, or conditions of activation.
- 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_69ca8329bb7c8190a63c643730839103 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cc46c5e8888190b721e791c449b0df |
completed | March 31, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69cc454504448190aaad2af8b17357cd |
completed | March 31, 2026, 10:05 p.m. |
Created at: March 30, 2026, 6:23 p.m.