Triple
T31520512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ring cycle |
E804193
|
entity |
| Predicate | firstPartPremiere |
P123605
|
FINISHED |
| Object | Das Rheingold |
E229315
|
NE 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: Das Rheingold | Statement: [Ring cycle, firstPartPremiere, Das Rheingold]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstPartPremiere Context triple: [Ring cycle, firstPartPremiere, Das Rheingold]
-
A.
secondPartPremiere
Indicates that the second part of a work (e.g., a series, film, or performance) has its premiere or first public showing at a specified time or event.
-
B.
премьера
Indicates that an entity has its first public showing, release, or debut (such as a film, play, or performance).
-
C.
firstPartSeries
chosen
Indicates that one entity is the initial installment or beginning segment in a series of related entities.
-
D.
partOfPremiereWork
Indicates that something is a component or segment belonging to a larger premiere work or initial presentation.
-
E.
firstAppearancePart
Indicates that an entity makes its first appearance as a component or segment within a larger work or sequence.
- F. None of above.
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_69f348cf839c81908657048402f7f97b |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a34665493888190a5e37d9d226920d2 |
completed | June 18, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_6a0379e7aa0c8190bdc9ee4d54fc821b |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 30, 2026, 9:55 p.m.