Triple
T37885506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waltz in A-flat major Op. 34 No. 1 |
E944983
|
entity |
| Predicate | followsInSet |
P125022
|
FINISHED |
| Object | Waltz in A minor Op. 34 No. 2 |
—
|
NE NERFINISHED |
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: Waltz in A minor Op. 34 No. 2 | Statement: [Waltz in A-flat major Op. 34 No. 1, followsInSet, Waltz in A minor Op. 34 No. 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsInSet Context triple: [Waltz in A-flat major Op. 34 No. 1, followsInSet, Waltz in A minor Op. 34 No. 2]
-
A.
followsIn
chosen
Indicates that one entity comes after or succeeds another in a sequence, order, or progression.
-
B.
followsFrom
Indicates that one fact, event, or state logically or causally results from, is implied by, or comes as a consequence of another.
-
C.
followsInSingle
Indicates that one entity immediately follows another in a sequence, with no other entities in between.
-
D.
followsBetween
Indicates that one entity comes after or succeeds another entity within a specified context or sequence.
-
E.
followsTo
Indicates that one entity moves or proceeds behind another entity toward a specific destination or target.
- 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_69f76ef02668819089e7940c4001af5e |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ff891e4b9c8190aa86a339a8944496 |
completed | May 9, 2026, 7:21 p.m. |
| PD | Predicate disambiguation | batch_69ff8801180c8190b23e20996ca68e0a |
completed | May 9, 2026, 7:16 p.m. |
Created at: May 3, 2026, 4:19 p.m.