Triple
T38592933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hellfire Shotguns |
E932494
|
entity |
| Predicate | primaryFire |
P206567
|
FINISHED |
| Object | Short-range spread blast |
—
|
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: Short-range spread blast | Statement: [Hellfire Shotguns, primaryFire, Short-range spread blast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryFire Context triple: [Hellfire Shotguns, primaryFire, Short-range spread blast]
-
A.
secondaryFire
Indicates the use or activation of an alternate or secondary mode of firing in a weapon or tool, distinct from its primary fire action.
-
B.
primaryForce
Indicates that one entity serves as the main or dominant force acting upon, influencing, or driving another entity or process.
-
C.
primaryCombat
Indicates that one entity is the main or principal opponent that another entity engages with in combat.
-
D.
primaryCatch
Indicates that an entity is the main or most significant target, recipient, or object captured or obtained in a given context.
-
E.
primaryFront
Indicates that one entity serves as the main or most important front-facing side or surface in relation to another entity.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037cae084081909004d77514c5f286 |
completed | May 12, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_6a037a2026248190b894436a578d79ac |
completed | May 12, 2026, 7:06 p.m. |
| PDg | Predicate description generation | batch_6a037c85e308819083dd67b96f457659 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:32 p.m.