Triple
T36113404
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Divine Poem (Symphony No. 3), Op. 43 |
E1044557
|
entity |
| Predicate | numberInComposerSymphonies |
P173491
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [Divine Poem (Symphony No. 3), Op. 43, numberInComposerSymphonies, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberInComposerSymphonies Context triple: [Divine Poem (Symphony No. 3), Op. 43, numberInComposerSymphonies, 3]
-
A.
numberOfSymphonies
Indicates the total count of symphonies associated with a given entity.
-
B.
workNumberInSymphoniesByComposer
chosen
Indicates the association between a specific work number and the symphonies composed by a particular composer.
-
C.
workNumberInMozartSymphonies
Indicates the ordinal position or catalog number that a given work holds within the collection of Mozart’s symphonies.
-
D.
workNumberInBeethovenSymphonies
Indicates the specific ordinal position a work holds within the set of Beethoven’s symphonies.
-
E.
workNumberInMahlerSymphonies
Indicates the specific numbered position a work occupies within the sequence of Mahler’s symphonies.
- 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_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0895b48190acdd88dc10db7be7 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:08 p.m.