Triple
T36961352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tome of Power |
E914314
|
entity |
| Predicate | weaponInteraction |
P161346
|
FINISHED |
| Object | modifies primary fire modes |
—
|
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: modifies primary fire modes | Statement: [Tome of Power, weaponInteraction, modifies primary fire modes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: weaponInteraction Context triple: [Tome of Power, weaponInteraction, modifies primary fire modes]
-
A.
weaponControl
Indicates that one entity has authority over, access to, or the ability to direct the use of a weapon associated with another entity.
-
B.
weaponControlMethod
chosen
Indicates how a weapon is operated, activated, or controlled in order to perform its intended function.
-
C.
weaponUsedOn
Indicates that a particular weapon was employed or applied against a specific target or entity.
-
D.
weaponUsedIn
Indicates that a particular weapon is employed or involved in carrying out a specific event or action.
-
E.
usedWeapon
Indicates that an entity employed a specific weapon as the means or tool to carry out an action or event.
- 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_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:14 p.m.