Triple
T8520305
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soirées musicales, Op. 6 |
E201677
|
entity |
| Predicate | languageOfTitleMeaning |
P56911
|
FINISHED |
| Object | Musical evenings |
—
|
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: Musical evenings | Statement: [Soirées musicales, Op. 6, languageOfTitleMeaning, Musical evenings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfTitleMeaning Context triple: [Soirées musicales, Op. 6, languageOfTitleMeaning, Musical evenings]
-
A.
nameMeaningLanguage
chosen
Indicates that a specified meaning of a name is expressed or interpreted in a particular language.
-
B.
titleMeaning
Indicates that one entity expresses or explains the meaning, significance, or interpretation of another entity’s title.
-
C.
languageOfTitleHolder
Indicates the language in which the title held by a given title holder is expressed or recorded.
-
D.
hasTitleEtymology
Indicates that the origin or derivation of a title is based on, or explained by, another term, name, or linguistic source.
-
E.
languageOfAlternativeTitle
Indicates the language in which an alternative or variant title of an entity is expressed.
- 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_69ca8321bb44819081b74df0b710276d |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe628f8c48190a35201f9fde605cc |
completed | March 31, 2026, 3:20 p.m. |
| PD | Predicate disambiguation | batch_69cbd10f64b4819080859057c19e58f0 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:16 p.m.