Triple
T36961366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tome of Power |
E914314
|
entity |
| Predicate | audioFeedback |
P22084
|
FINISHED |
| Object | alters weapon sound effects |
—
|
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: alters weapon sound effects | Statement: [Tome of Power, audioFeedback, alters weapon sound effects]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: audioFeedback Context triple: [Tome of Power, audioFeedback, alters weapon sound effects]
-
A.
receivesAuditoryFeedbackInformation
Indicates that an entity obtains information through auditory feedback, such as sounds or spoken responses, resulting from its actions or environment.
-
B.
voiceOutcome
Indicates the result or consequence produced by a particular voice action, command, or vocal interaction.
-
C.
usesSound
Indicates that one entity employs or relies on sound as a means or tool in relation to another entity or context.
-
D.
auditoryIconOf
Indicates that one entity is an auditory icon that sonically represents, symbolizes, or stands in for another entity or concept.
-
E.
hasSound
chosen
Indicates that an entity produces, emits, or is associated with a particular sound.
- 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.