Triple
T36836068
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sturmgewehr 44 |
E910273
|
entity |
| Predicate | hasRateOfFireClass |
P17731
|
FINISHED |
| Object | high rate of fire |
—
|
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: high rate of fire | Statement: [Sturmgewehr 44, hasRateOfFireClass, high rate of fire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRateOfFireClass Context triple: [Sturmgewehr 44, hasRateOfFireClass, high rate of fire]
-
A.
rateOfFire
chosen
Indicates the frequency at which a weapon or system can discharge projectiles or shots over a given period of time.
-
B.
hasFiringRange
Indicates that one entity possesses or provides a designated area or capability for discharging weapons over a specified distance.
-
C.
gunRate
Indicates the rate or frequency at which guns are present, owned, used, or involved in incidents within a given context.
-
D.
weaponSpeed
Indicates the relative quickness or rate at which a weapon can be used or strikes can be executed.
-
E.
hasFireControlSystem
Indicates that an entity is equipped with or includes a fire control system used to detect, track, and direct weapons or suppression against targets.
- 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_69fdb04ed81c8190b8feea90c1c785a6 |
completed | May 8, 2026, 9:43 a.m. |
| PD | Predicate disambiguation | batch_69fda9d6c5148190a63205b6d9b0a1b4 |
completed | May 8, 2026, 9:16 a.m. |
Created at: May 3, 2026, 4:13 p.m.