Triple
T29026773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Schumann’s symphonies |
E737613
|
entity |
| Predicate | firstSymphonyComposed |
P202357
|
FINISHED |
| Object | Symphony No. 1 in B-flat major, Op. 38 |
—
|
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: Symphony No. 1 in B-flat major, Op. 38 | Statement: [Schumann’s symphonies, firstSymphonyComposed, Symphony No. 1 in B-flat major, Op. 38]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstSymphonyComposed Context triple: [Schumann’s symphonies, firstSymphonyComposed, Symphony No. 1 in B-flat major, Op. 38]
-
A.
firstConcertoComposed
Indicates that the subject is the first concerto ever composed by, or attributed to, the object.
-
B.
secondSymphonyComposed
Indicates that an entity composed the second symphony associated with another entity (typically a composer and their second symphonic work).
-
C.
firstBalladeComposed
Indicates that the subject is the entity for which the object is the first ballade that they composed.
-
D.
earlyWorkOfComposer
Indicates that a work is among the earlier compositions created by a particular composer.
-
E.
numberOfSymphonies
Indicates the total count of symphonies associated with a given 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_69f077ef00fc81909325f084ad37c035 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_6a0076c0a5c4819088b17b95511b93ed |
completed | May 10, 2026, 12:14 p.m. |
| PD | Predicate disambiguation | batch_6a007638a67c81909c091335142260ab |
completed | May 10, 2026, 12:12 p.m. |
| PDg | Predicate description generation | batch_6a0076bfd1a481909170c3e181a16d9a |
completed | May 10, 2026, 12:14 p.m. |
Created at: April 28, 2026, 9:53 a.m.