Triple
T21913889
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ut queant laxis |
E541131
|
entity |
| Predicate | originalSolfègeSyllable |
P145616
|
FINISHED |
| Object | ut |
—
|
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: ut | Statement: [Ut queant laxis, originalSolfègeSyllable, ut]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalSolfègeSyllable Context triple: [Ut queant laxis, originalSolfègeSyllable, ut]
-
A.
tonalSystem
Indicates a relationship where a language or musical system is characterized by a specific set of tonal patterns or pitch distinctions that structure its sounds or expressions.
-
B.
musicalSymbol
Indicates that one entity is a musical notation mark or sign associated with another entity in a musical context.
-
C.
languageOfSyllables
Indicates a relationship where a language is characterized or defined by the specific set or system of syllables it uses.
-
D.
diatonicScale
Indicates that a musical element (such as a note, chord, or melody) belongs to or is derived from a specific diatonic scale.
-
E.
usesSyllables
Indicates that one entity forms, expresses, or analyzes something by employing syllables as its basic units.
- 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_69e0c47c4b9c8190a5586a75f5f36453 |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f123359e1c8190a606a92c5bcb58e8 |
completed | April 28, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69e6be9ebf4c8190892df1a8e1313f88 |
completed | April 21, 2026, 12:02 a.m. |
| PDg | Predicate description generation | batch_69e6c187bc548190b4ca13150f6bae38 |
completed | April 21, 2026, 12:15 a.m. |
Created at: April 16, 2026, 7:42 p.m.