Triple
T38592358
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pulse Pistols |
E932482
|
entity |
| Predicate | primaryFireMode |
P9011
|
FINISHED |
| Object | rapid-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: rapid-fire | Statement: [Pulse Pistols, primaryFireMode, rapid-fire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryFireMode Context triple: [Pulse Pistols, primaryFireMode, rapid-fire]
-
A.
fireModes
chosen
Indicates the different ways or settings in which a weapon or device can be fired or operated.
-
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.
rateOfFire
Indicates the frequency at which a weapon or system can discharge projectiles or shots over a given period of time.
-
D.
primaryShooter
Indicates that the subject is the main individual responsible for firing a weapon in the referenced event or context.
-
E.
fireControlFeature
Indicates a relationship where an entity possesses or is associated with a capability or mechanism for directing, managing, or controlling the use of fire or weapon fire.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a2026248190b894436a578d79ac |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:32 p.m.