Triple
T27685218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wagner’s Der Ring des Nibelungen under Daniel Barenboim |
E698007
|
entity |
| Predicate | includesOpera |
P27848
|
FINISHED |
| Object | Das Rheingold |
—
|
NE NERFINISHED |
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: Das Rheingold | Statement: [Wagner’s Der Ring des Nibelungen under Daniel Barenboim, includesOpera, Das Rheingold]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesOpera Context triple: [Wagner’s Der Ring des Nibelungen under Daniel Barenboim, includesOpera, Das Rheingold]
-
A.
isOnlyOperaBy
Indicates that a given opera is the sole opera composed by a particular creator.
-
B.
appearsInOperaBy
Indicates that one entity (typically a character, role, or element) is featured or takes part in an opera created or composed by another entity.
-
C.
fromOperaSetIn
Indicates that an opera originates from or is part of a narrative that is set in a particular place or setting.
-
D.
operatesSystem
Indicates that an entity actively controls, manages, or runs a particular system.
-
E.
operaComponent
chosen
Indicates that one entity is a constituent part or section of an opera associated with the other entity.
- 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_69ef590df8708190af5488f0638e790c |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69fe30bc64308190b603ff1b30c2aeee |
completed | May 8, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fe2f7175b081908dd61e1513620bbe |
completed | May 8, 2026, 6:46 p.m. |
Created at: April 27, 2026, 2:49 p.m.