Triple
T32902556
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vienna version |
E841649
|
entity |
| Predicate | hasRevisedScoreComparedTo |
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, hasRevisedScoreComparedTo, Dresden version]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRevisedScoreComparedTo Context triple: [Vienna version, hasRevisedScoreComparedTo, Dresden version]
-
A.
hasOriginalScoreFor
Indicates that one entity is the original musical score specifically composed for another entity, such as a film, show, or performance.
-
B.
hasRevisedOrigin
Indicates that the origin of an entity has been updated or modified from its previous or initial state.
-
C.
includesNewScoreBy
Indicates that an entity incorporates or contains a newly added score produced by another entity.
-
D.
hasScoreBy
Indicates that one entity possesses or is associated with a score that was assigned, produced, or determined by another entity.
-
E.
hasModificationComparedTo
chosen
Indicates that one entity differs from another by having a specific change, adjustment, or alteration relative to it.
- 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_6a031c6c728c81909c1d010048df71c3 |
completed | May 12, 2026, 12:26 p.m. |
| PD | Predicate disambiguation | batch_6a031bfc3b74819098c551096b1fcf00 |
completed | May 12, 2026, 12:24 p.m. |
Created at: May 1, 2026, 1:19 a.m.