Triple
T31520666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rhinemaidens |
E804196
|
entity |
| Predicate | operaNumberInCycle |
P200845
|
FINISHED |
| Object | 1 (Das Rheingold) |
—
|
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: 1 (Das Rheingold) | Statement: [Rhinemaidens, operaNumberInCycle, 1 (Das Rheingold)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operaNumberInCycle Context triple: [Rhinemaidens, operaNumberInCycle, 1 (Das Rheingold)]
-
A.
operaNumberInComposerOutput
Indicates the ordinal position or catalog number assigned to an opera within the complete body of works by a specific composer.
-
B.
movementNumberInOpera
Indicates the specific numbered position that a musical movement occupies within an opera.
-
C.
numberOfOperas
Indicates the total count of operas associated with a given entity (such as a person, organization, or catalog entry).
-
D.
operaNumberType
Indicates the type or classification assigned to an opera’s identifying number within a cataloging or numbering system.
-
E.
estimatedNumberOfOperas
Indicates the approximate count of operas associated with an entity, rather than an exact, verified number.
- 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_69f348cf839c81908657048402f7f97b |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69ffb1f0b03c81909ddb81f07ce74e88 |
completed | May 9, 2026, 10:15 p.m. |
| PD | Predicate disambiguation | batch_69ffb1662b2481908582e0612744f4c5 |
completed | May 9, 2026, 10:12 p.m. |
| PDg | Predicate description generation | batch_69ffb1f001948190a63c493b596a97b9 |
completed | May 9, 2026, 10:15 p.m. |
Created at: April 30, 2026, 9:55 p.m.