Triple
T12013498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Symphony No. 101 in D major "The Clock" |
E285963
|
entity |
| Predicate | workNumberInHaydnSymphonies |
P86651
|
FINISHED |
| Object | 101 |
—
|
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: 101 | Statement: [Symphony No. 101 in D major "The Clock", workNumberInHaydnSymphonies, 101]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workNumberInHaydnSymphonies Context triple: [Symphony No. 101 in D major "The Clock", workNumberInHaydnSymphonies, 101]
-
A.
workNumberInHaydnOutput
chosen
Indicates the ordinal number assigned to a specific work within the catalog of Haydn’s compositions.
-
B.
workNumberInMahlerSymphonies
Indicates the specific numbered position a work occupies within the sequence of Mahler’s symphonies.
-
C.
workNumberWithinLondonSymphonies
Indicates the numerical position or identifier assigned to a work within the set of London Symphonies.
-
D.
numberOfSymphonies
Indicates the total count of symphonies associated with a given entity.
-
E.
workNumberInComposerChamberMusic
Indicates that a specific work number is assigned to a composer's piece within their body of chamber music.
- 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_69d6ab45a368819084fce08bf0dc3705 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d903d884488190b4450a98088208ef |
completed | April 10, 2026, 2:06 p.m. |
| PD | Predicate disambiguation | batch_69d902b245cc8190af96a9c2bd9c6250 |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:46 p.m.