Triple
T29325962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | English horn |
E743643
|
entity |
| Predicate | hasPitchRange |
P1151
|
FINISHED |
| Object | lower than oboe |
—
|
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: lower than oboe | Statement: [English horn, hasPitchRange, lower than oboe]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPitchRange Context triple: [English horn, hasPitchRange, lower than oboe]
-
A.
hasPitch
Indicates that one entity possesses or is characterized by a specific pitch (such as a tonal, acoustic, or frequency-related property).
-
B.
hasPitchLength
Indicates that an entity (such as a field or pitch) is associated with a specific measurement of its length.
-
C.
hasMelodicRange
Indicates that a musical piece, phrase, or part spans a specific interval between its lowest and highest pitches.
-
D.
hasPitchShape
Indicates that one entity possesses or exhibits a particular contour, form, or configuration of pitch.
-
E.
vocalRange
chosen
Indicates the span of pitches or notes that an entity (such as a singer or instrument) is capable of producing.
- 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_69f09125f784819080f4e9fce9fe624f |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c4abec8190bc2379e66f4af0a9 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 28, 2026, 1:26 p.m.