Triple
T5141499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | American popular music standards repertoire |
E115962
|
entity |
| Predicate | typicalHarmony |
P12230
|
FINISHED |
| Object | functional tonal harmony |
—
|
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: functional tonal harmony | Statement: [American popular music standards repertoire, typicalHarmony, functional tonal harmony]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalHarmony Context triple: [American popular music standards repertoire, typicalHarmony, functional tonal harmony]
-
A.
hasHarmony
Indicates that two or more entities are in a state of balance, agreement, or pleasing coordination with one another.
-
B.
typicalIn
chosen
Indicates that something commonly occurs, appears, or is found within a given context, category, or environment.
-
C.
typicalPerformance
Indicates the usual or characteristic level at which an entity performs under normal conditions.
-
D.
typicalVariety
Indicates that one entity is a representative or characteristic example of the variety or type defined by another entity.
-
E.
typicalConsistency
Indicates that one entity characteristically maintains a regular or expected level of consistency in relation to another entity or context.
- 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_69bd44459a988190a772a5c2ec6a1965 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd78d7f4d081908d59adcd86f52f1d |
completed | March 20, 2026, 4:42 p.m. |
| PD | Predicate disambiguation | batch_69bd77ae2f10819098bb8939106e1281 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:43 p.m.