Triple
T32902560
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vienna version |
E841649
|
entity |
| Predicate | hasRevisedDramaturgyComparedTo |
—
|
GENERATED |
| Object | Dresden version |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRevisedDramaturgyComparedTo Context triple: [Vienna version, hasRevisedDramaturgyComparedTo, Dresden version]
-
A.
revisedForTheatre
Indicates that a work has been adapted or modified specifically for performance in a theatrical setting.
-
B.
hasChoreographicRevisionsBy
Indicates that a work’s choreography has been revised or altered by a specified person or entity.
-
C.
revisedPremiereTheatre
Indicates that an entity has updated or altered the initial theatrical premiere of another entity (such as a film, play, or performance).
-
D.
revisionOf
chosen
Indicates that one entity is a modified or updated version of another earlier entity.
-
E.
basedOnLibrettoRevisionBy
Indicates that something (typically a musical or operatic work or version) is derived from or created using a revised form of a libretto produced by a specified reviser.
- F. None of above.
Provenance (1 batch)
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_69f34946a5208190bbd79f0fec4323bd |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:19 a.m.