Triple
T19069822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pan flute |
E466761
|
entity |
| Predicate | pitchAdjustedBy |
P78031
|
FINISHED |
| Object | partially covering pipe openings |
—
|
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: partially covering pipe openings | Statement: [Pan flute, pitchAdjustedBy, partially covering pipe openings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pitchAdjustedBy Context triple: [Pan flute, pitchAdjustedBy, partially covering pipe openings]
-
A.
pitchConvertedTo
Indicates that one pitch has been transformed or translated into another pitch or pitch representation.
-
B.
pitchAlterationMechanism
chosen
Indicates the mechanism or method by which the pitch of a sound or signal is changed or controlled.
-
C.
stripPitch
Indicates removing the pitch or tonal information from an audio signal or sound representation, leaving only non-pitch-related characteristics.
-
D.
relativePitch
Indicates a relationship where one entity’s pitch is defined or compared in terms of its interval or distance from another entity’s pitch.
-
E.
hasPitch
Indicates that one entity possesses or is characterized by a specific pitch (such as a tonal, acoustic, or frequency-related property).
- 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_69d8dd04f4488190b1121cc53ef2bfd6 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5e19caa708190876a2cb06aa0c9cc |
completed | April 20, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69e4b99f602881909eeb9c780597e0e6 |
completed | April 19, 2026, 11:16 a.m. |
Created at: April 10, 2026, 12:03 p.m.