Triple
T32902558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vienna version |
E841649
|
entity |
| Predicate | hasRevisedOrchestrationComparedTo |
—
|
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: hasRevisedOrchestrationComparedTo Context triple: [Vienna version, hasRevisedOrchestrationComparedTo, Dresden version]
-
A.
hasRevisedOrigin
Indicates that the origin of an entity has been updated or modified from its previous or initial state.
-
B.
hasModificationComparedTo
chosen
Indicates that one entity differs from another by having a specific change, adjustment, or alteration relative to it.
-
C.
hasChoreographicRevisionsBy
Indicates that a work’s choreography has been revised or altered by a specified person or entity.
-
D.
orchestrationRevisedBy
Indicates that an existing orchestration has been modified or updated by another orchestration or revision entity.
-
E.
hasOrchestration
Indicates that one entity coordinates, manages, or sequences the actions or interactions of another entity or set of entities.
- 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.