Triple
T6383282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ahavah Rabbah mode |
E143637
|
entity |
| Predicate | tonalCenterTypical |
P49862
|
FINISHED |
| Object | D |
—
|
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: D | Statement: [Ahavah Rabbah mode, tonalCenterTypical, D]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tonalCenterTypical Context triple: [Ahavah Rabbah mode, tonalCenterTypical, D]
-
A.
tonalCenter
Indicates that one musical element functions as the primary pitch or key center around which another musical element is organized.
-
B.
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).
-
C.
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.
-
D.
typicalIn
Indicates that something commonly occurs, appears, or is found within a given context, category, or environment.
-
E.
typicalBase
chosen
Indicates that one entity serves as the standard or most representative base or foundation for another entity in typical or common cases.
- 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_69c008dac1ec81909cef8157ccd69962 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c06854eb608190acb6bb4dc466f0fc |
completed | March 22, 2026, 10:08 p.m. |
| PD | Predicate disambiguation | batch_69c060eff524819094cee1c70a0c1ff4 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:34 p.m.