Triple
T32902558
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vienna version |
E841649
|
entity |
| Predicate | hasRevisedOrchestrationComparedTo |
P200656
|
FINISHED |
| Object | Dresden version |
—
|
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: Dresden version | Statement: [Vienna version, hasRevisedOrchestrationComparedTo, Dresden version]
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 (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_69f34946a5208190bbd79f0fec4323bd |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a03213d35788190bdf04e19625b4060 |
completed | May 12, 2026, 12:46 p.m. |
| PD | Predicate disambiguation | batch_6a031ea131d48190ab0fecb48b8e2205 |
completed | May 12, 2026, 12:35 p.m. |
Created at: May 1, 2026, 1:19 a.m.