Triple
T36113245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Piano Sonata No. 10, Op. 70 |
E1044553
|
entity |
| Predicate | opusFollows |
P134
|
FINISHED |
| Object | Piano Sonata No. 9, Op. 68 |
—
|
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: Piano Sonata No. 9, Op. 68 | Statement: [Piano Sonata No. 10, Op. 70, opusFollows, Piano Sonata No. 9, Op. 68]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opusFollows Context triple: [Piano Sonata No. 10, Op. 70, opusFollows, Piano Sonata No. 9, Op. 68]
-
A.
eraFollowed
Indicates that one historical era comes directly after another in chronological sequence.
-
B.
followsDisc
Indicates that one entity comes after another in a sequence or order, typically in a discrete or stepwise progression.
-
C.
adoptedFollowing
Indicates that one entity formally took on or implemented another entity after or as a result of the occurrence of a preceding event, state, or action.
-
D.
follows
chosen
Indicates that one entity comes after, moves behind, or acts in accordance with another entity in time, space, or sequence.
-
E.
followsTopic
Indicates that one entity subscribes to or tracks updates, content, or activity related to a particular topic associated with another entity.
- 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_69f76e344a4c8190af3858c6d78ba88f |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b3e2f3c08190be4fd1ae4fa1266d |
completed | May 3, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69f7b1bcc47081909fe7d592ac69006c |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 3, 2026, 4:08 p.m.