Triple
T36958277
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heavy Weapon Dude |
E914242
|
entity |
| Predicate | firingStyle |
P75588
|
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: [Heavy Weapon Dude, firingStyle, rapid fire]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firingStyle Context triple: [Heavy Weapon Dude, firingStyle, rapid fire]
-
A.
firing
Indicates initiating the discharge of a weapon or explosive device toward a target.
-
B.
firingCharacteristic
chosen
Indicates the specific way in which an entity initiates or sustains firing or discharge, such as its pattern, mode, or conditions of activation.
-
C.
firingDetail
Indicates that one entity performs or is involved in a specific act of firing (such as discharging a weapon or initiating a shot) toward or in relation to another entity, including contextual details of that firing event.
-
D.
fireModes
Indicates the different ways or settings in which a weapon or device can be fired or operated.
-
E.
shootingStyle
Indicates the characteristic manner or technique with which an entity performs a shooting action (e.g., in sports or photography).
- 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_69f76e8c498c8190b2842db80aea8b3b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb34e5576881909394355c8ec6ddd2 |
completed | May 6, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69fb2f6171e88190bf1e0ee6a644b6a9 |
completed | May 6, 2026, 12:09 p.m. |
Created at: May 3, 2026, 4:13 p.m.