Triple
T28856383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | B-flat clarinet |
E728748
|
entity |
| Predicate | hasStandardTuningPitch |
P49771
|
FINISHED |
| Object | A4 = 440 Hz reference |
—
|
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: A4 = 440 Hz reference | Statement: [B-flat clarinet, hasStandardTuningPitch, A4 = 440 Hz reference]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStandardTuningPitch Context triple: [B-flat clarinet, hasStandardTuningPitch, A4 = 440 Hz reference]
-
A.
hasTuningDivision
Indicates that one entity specifies or uses a particular system or scheme for dividing a range (such as a musical interval or scale) into tuning units.
-
B.
commonlySetToTune
Indicates that something is frequently assigned or adjusted to a particular tune or musical setting.
-
C.
tunedOrUntuned
Indicates whether something is in a properly adjusted or calibrated state (tuned) or not (untuned).
-
D.
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.
-
E.
hasPitch
chosen
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_69f0319f4e5481909e4c439dbe8be940 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69fd76d1e5208190a6f26651492d1e3c |
completed | May 8, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69fd702a226c81908edfda00f4be4130 |
completed | May 8, 2026, 5:10 a.m. |
Created at: April 28, 2026, 6:45 a.m.