Triple
T19895779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hammond organ |
E478147
|
entity |
| Predicate | hasPedalboardRange |
P137741
|
FINISHED |
| Object | 25-note pedalboard in many models |
—
|
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: 25-note pedalboard in many models | Statement: [Hammond organ, hasPedalboardRange, 25-note pedalboard in many models]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPedalboardRange Context triple: [Hammond organ, hasPedalboardRange, 25-note pedalboard in many models]
-
A.
hasPedal
Indicates that one entity possesses or is equipped with a pedal or pedals used for operation or control.
-
B.
hasFrets
Indicates that an instrument or similar object possesses frets, i.e., raised elements on its neck or surface that divide it into fixed pitch intervals.
-
C.
hasGuitarEffect
Indicates that one entity applies, uses, or is associated with a particular guitar effect in relation to another entity.
-
D.
hasBandRange
Indicates that one entity has an associated range or span of bands (such as frequency or wavelength intervals) defined by the other entity.
-
E.
hasFingerboardWood
Indicates that one entity uses or features the other as the material of its fingerboard.
- 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_69d8e520682081909892916424699bd5 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6593cb45881909cc34a9c601db001 |
completed | April 20, 2026, 4:50 p.m. |
| PD | Predicate disambiguation | batch_69e537ecda248190895c96afb6243823 |
completed | April 19, 2026, 8:15 p.m. |
| PDg | Predicate description generation | batch_69e543c136b081909cab9394b958390a |
completed | April 19, 2026, 9:06 p.m. |
Created at: April 10, 2026, 1:52 p.m.