Triple
T35281067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | E-flat clarinet |
E1018933
|
entity |
| Predicate | hasPitchCharacteristic |
P38697
|
FINISHED |
| Object | high-pitched |
—
|
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: high-pitched | Statement: [E-flat clarinet, hasPitchCharacteristic, high-pitched]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPitchCharacteristic Context triple: [E-flat clarinet, hasPitchCharacteristic, high-pitched]
-
A.
hasPitch
Indicates that one entity possesses or is characterized by a specific pitch (such as a tonal, acoustic, or frequency-related property).
-
B.
hasPitchShape
Indicates that one entity possesses or exhibits a particular contour, form, or configuration of pitch.
-
C.
hasPitchLength
Indicates that an entity (such as a field or pitch) is associated with a specific measurement of its length.
-
D.
hasPitchBarrier
Indicates that there is a physical or structural barrier affecting or limiting the pitch (height or angle) between related entities.
-
E.
hasPitchType
chosen
Indicates that an entity is associated with, or characterized by, a specific type or category of pitch.
- 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_69f76de6d39c8190bb11342e4b91ff2b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78fdaeaf88190a6b24a96634ddfe1 |
completed | May 3, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_69f78e2f52e08190a77661223a96c601 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:03 p.m.