Triple
T30847077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Les Noces |
E785665
|
entity |
| Predicate | hasChoralText |
P193362
|
FINISHED |
| Object | Old Russian and folk-inspired verses |
—
|
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: Old Russian and folk-inspired verses | Statement: [Les Noces, hasChoralText, Old Russian and folk-inspired verses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChoralText Context triple: [Les Noces, hasChoralText, Old Russian and folk-inspired verses]
-
A.
hasChoralArrangement
Indicates that one entity is a choral arrangement version or setting of another entity (typically an original musical work).
-
B.
hasChoir
Indicates that an entity possesses, maintains, or is associated with a choir.
-
C.
hasChorusStyle
Indicates that an entity is associated with a particular style or manner in which a chorus is performed or structured.
-
D.
hasChorusLanguage
Indicates that the language used in the chorus section of a work (such as a song or musical piece) is a specified language.
-
E.
usesChorale
Indicates that one entity incorporates or employs a chorale (a hymn-like musical piece) within its structure or content.
- 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_69f224b850848190a4af4ccf8ddadcdf |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fd44474ed48190ac372e4c88d762ed |
completed | May 8, 2026, 2:02 a.m. |
| PD | Predicate disambiguation | batch_69fd41ef28a48190a66959be5c964461 |
completed | May 8, 2026, 1:52 a.m. |
| PDg | Predicate description generation | batch_69fd4445f8c08190bb2dc27e0971c55d |
completed | May 8, 2026, 2:02 a.m. |
Created at: April 29, 2026, 8:46 p.m.