Triple
T10980285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aeolian organ |
E259484
|
entity |
| Predicate | soundProductionMethod |
P75977
|
FINISHED |
| Object | air-driven pipes |
—
|
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: air-driven pipes | Statement: [Aeolian organ, soundProductionMethod, air-driven pipes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: soundProductionMethod Context triple: [Aeolian organ, soundProductionMethod, air-driven pipes]
-
A.
soundReproductionMethod
Indicates the method or technique used to reproduce or play back sound.
-
B.
soundEngineering
Indicates the relationship in which an entity designs, manipulates, or manages audio elements and acoustics for recording, production, or live sound.
-
C.
soundDesignBy
Indicates that the sound design for a work (such as a film, game, or performance) is created or supervised by a particular person or entity.
-
D.
soundEngine
Indicates that one entity functions as or provides the sound engine (audio processing or synthesis system) used by another entity.
-
E.
primarySoundProduction
chosen
Indicates that one entity is the main means or mechanism by which sound is produced for another entity.
- 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_69d6aa895f4c8190887a15460ef622f4 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d772e97cf88190a65dab3ec4e5f7f3 |
completed | April 9, 2026, 9:35 a.m. |
| PD | Predicate disambiguation | batch_69d72e9055908190b438f039574aaaaf |
completed | April 9, 2026, 4:44 a.m. |
Created at: April 8, 2026, 9:24 p.m.