Triple
T25384948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bloodpack |
E631495
|
entity |
| Predicate | notableWeaponry |
P151929
|
FINISHED |
| Object | firearms |
—
|
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: firearms | Statement: [Bloodpack, notableWeaponry, firearms]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableWeaponry Context triple: [Bloodpack, notableWeaponry, firearms]
-
A.
hasNotableWeaponNamedAfter
Indicates that an entity possesses a notable weapon that is named after another specific entity.
-
B.
featuredWeapon
chosen
Indicates that a particular weapon is highlighted or prominently showcased in relation to an entity, such as a character, event, or context.
-
C.
weaponOfInterest
Indicates that an entity is a weapon that is specifically relevant, notable, or targeted for attention within a given context or scenario.
-
D.
weaponsUsed
Indicates that one entity employed or utilized another entity as a weapon in carrying out an action or event.
-
E.
weaponsRepresent
Indicates that certain weapons serve as symbols or embodiments of something, such as ideas, groups, or values.
- 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_69e75a8c50788190aabaa9f96710fc43 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69fbc9d1dba881908c399b8e1dc13ce2 |
completed | May 6, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69fbc8ec03ac8190a757563f96fab283 |
completed | May 6, 2026, 11:04 p.m. |
Created at: April 21, 2026, 1:46 p.m.