Triple
T37539796
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sonic Amplifier |
E933295
|
entity |
| Predicate | alternateFireFunction |
P99961
|
FINISHED |
| Object | sound wave knockback |
—
|
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: sound wave knockback | Statement: [Sonic Amplifier, alternateFireFunction, sound wave knockback]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: alternateFireFunction Context triple: [Sonic Amplifier, alternateFireFunction, sound wave knockback]
-
A.
alternateWith
Indicates that one entity occurs, appears, or is arranged in succession with another, taking turns or interchanging in sequence.
-
B.
secondaryFire
chosen
Indicates the use or activation of an alternate or secondary mode of firing in a weapon or tool, distinct from its primary fire action.
-
C.
alternateMode
Indicates that one entity functions as an alternative form, configuration, or mode of operation for another entity.
-
D.
alternativeImplementation
Indicates that one implementation serves as a substitute or different way of realizing the same functionality or specification as another implementation.
-
E.
selectFire
Indicates choosing or designating a specific fire source, mode, or target for use or activation.
- 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_69f76ec999288190ae26ec7b6aea7046 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb084760c8190a1554985d3c3cb7a |
completed | May 6, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69fbadf3cb548190ba3b7514f76b790a |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:17 p.m.