Triple
T32738701
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hijaz scale |
E837160
|
entity |
| Predicate | containsTetrachord |
P201378
|
FINISHED |
| Object | Hijaz tetrachord |
—
|
NE NERFINISHED |
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: Hijaz tetrachord | Statement: [Hijaz scale, containsTetrachord, Hijaz tetrachord]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsTetrachord Context triple: [Hijaz scale, containsTetrachord, Hijaz tetrachord]
-
A.
usesChord
Indicates that one entity employs or incorporates a particular chord in its structure, performance, or composition.
-
B.
hasChordProgressionType
Indicates that a musical piece, section, or passage exhibits a specific type or pattern of chord progression.
-
C.
chorusContains
Indicates that a chorus includes or is composed of the specified element(s) as part of its content.
-
D.
usesChordChangesOf
Indicates that one musical work employs the same or substantially similar chord progression as another work.
-
E.
containsChorusOf
Indicates that one entity (typically a musical work or section) includes within it a chorus performed by another entity (such as a group of singers or ensemble).
- F. None of above. chosen
Provenance (4 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_69f34936e1748190b797e406e4e9293a |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ffef812da48190b875a7376b24f92d |
completed | May 10, 2026, 2:37 a.m. |
| PD | Predicate disambiguation | batch_69ffedecd580819097851b1473fdd6ed |
completed | May 10, 2026, 2:31 a.m. |
| PDg | Predicate description generation | batch_69ffef8003c081909ec2413b4ea08d43 |
completed | May 10, 2026, 2:37 a.m. |
Created at: May 1, 2026, 1:12 a.m.