Triple
T16901751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | F major |
E424453
|
entity |
| Predicate | leadingTone |
P125130
|
FINISHED |
| Object | E |
—
|
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: E | Statement: [F major, leadingTone, E]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leadingTone Context triple: [F major, leadingTone, E]
-
A.
tonal
Indicates that one entity has a tone, pitch pattern, or tonal quality in relation to another (such as a language, sound, or musical element).
-
B.
tonalCharacteristic
Indicates the specific quality or character of a sound’s tone, such as its color, texture, or expressive nuance, in relation to an entity.
-
C.
inTonality
Indicates that something (such as a musical element, passage, or piece) is expressed, structured, or interpreted within a specific musical key or tonal framework.
-
D.
topNote
Indicates that one entity serves as the primary or highest-level note associated with another entity.
-
E.
marksTones
Indicates that one entity applies or denotes tonal markings or distinctions on another entity, such as in language or notation.
- 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_69d889da3e8c8190a2b118f383f0beac |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e3c8dc7cf08190ad935935d8daf1d0 |
completed | April 18, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69e32b9489408190bcb2ede567ff5bf9 |
completed | April 18, 2026, 6:58 a.m. |
| PDg | Predicate description generation | batch_69e34fb7c8c8819086975b7955b7d8ef |
completed | April 18, 2026, 9:32 a.m. |
Created at: April 10, 2026, 5:29 a.m.