Triple
T3236160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Blue Danube |
E67859
|
entity |
| Predicate | laterVersion |
P47516
|
FINISHED |
| Object | orchestral 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: orchestral version | Statement: [The Blue Danube, laterVersion, orchestral version]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterVersion Context triple: [The Blue Danube, laterVersion, orchestral version]
-
A.
laterCompletionVersion
Indicates that one entity is a version of a completion that occurs or is produced later in time than another related version.
-
B.
latestVersion
Indicates that one entity is the most recent or up-to-date version of another entity within a sequence or set of versions.
-
C.
laterVersionSyntax
Indicates that one syntax form is a newer or more updated version of another syntax form.
-
D.
laterPlatform
Indicates that one entity occurs, appears, or is positioned on a platform that comes after another platform in time or sequence.
-
E.
laterReleased
Indicates that one entity was released at a time chronologically after the release of another entity.
- 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_69ad858d27348190abb61c280b4c86a9 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaee05d34819095dbce4db6ac8613 |
completed | March 8, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69ada4159e0481908cbbdd750f5e08c7 |
completed | March 8, 2026, 4:30 p.m. |
| PDg | Predicate description generation | batch_69ada698eeb48190a1f5762fdd3b7b63 |
completed | March 8, 2026, 4:40 p.m. |
Created at: March 8, 2026, 3:08 p.m.