Triple
T26195023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eruption |
E655073
|
entity |
| Predicate | amplifierUsed |
P136179
|
FINISHED |
| Object | Marshall amplifier (modified) |
—
|
NE NERFINISHED |
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: Marshall amplifier (modified) | Statement: [Eruption, amplifierUsed, Marshall amplifier (modified)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: amplifierUsed Context triple: [Eruption, amplifierUsed, Marshall amplifier (modified)]
-
A.
hasNumberOfAmplifierChannels
Indicates the relationship that specifies how many amplifier channels are present or supported in the associated entity.
-
B.
hasAmplifierType
chosen
Indicates that an entity is associated with, or characterized by, a specific type or category of amplifier used.
-
C.
amplificationMechanism
Indicates the process or mechanism by which a signal, effect, or influence is increased in strength, magnitude, or impact.
-
D.
hasAcousticUse
Indicates that something is used or functions in relation to sound or acoustics.
-
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.
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_69ee5b48236c81908fe385b6afc4f60b |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69f60ca50d0081909d146f3c697227aa |
completed | May 2, 2026, 2:39 p.m. |
| PD | Predicate disambiguation | batch_69f5b007ec1c819092e2c3605933f60b |
completed | May 2, 2026, 8:04 a.m. |
Created at: April 26, 2026, 8:46 p.m.