Triple
T32738597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mr. Eliminator |
E837157
|
entity |
| Predicate | hasReverbUsage |
P204019
|
FINISHED |
| Object | heavy spring reverb |
—
|
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: heavy spring reverb | Statement: [Mr. Eliminator, hasReverbUsage, heavy spring reverb]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReverbUsage Context triple: [Mr. Eliminator, hasReverbUsage, heavy spring reverb]
-
A.
hasAcousticUse
Indicates that something is used or functions in relation to sound or acoustics.
-
B.
hasAcousticsSuitableFor
Indicates that something possesses acoustic properties that are appropriate or well-suited for a particular use, activity, or environment.
-
C.
hasAcousticsType
Indicates the specific kind or quality of acoustic characteristics associated with an entity.
-
D.
usesSound
Indicates that one entity employs or relies on sound as a means or tool in relation to another entity or context.
-
E.
usesInstrument
Indicates that an agent performs an action by employing a specific instrument or tool as the means to carry it out.
- 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_69f34936e1748190b797e406e4e9293a |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a030d3db2748190b32fcf7b21bd0d0a |
completed | May 12, 2026, 11:21 a.m. |
| PD | Predicate disambiguation | batch_6a030ca6bf388190b2f6931376323da3 |
completed | May 12, 2026, 11:19 a.m. |
| PDg | Predicate description generation | batch_6a030d3d14b48190a1858d37988e7fd6 |
completed | May 12, 2026, 11:21 a.m. |
Created at: May 1, 2026, 1:12 a.m.