Triple
T31763314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Symphony No. 1 in C minor, Op. 11 |
E810739
|
entity |
| Predicate | MendelssohnSymphonyNumbering |
P172276
|
FINISHED |
| Object | No. 1 |
—
|
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: No. 1 | Statement: [Symphony No. 1 in C minor, Op. 11, MendelssohnSymphonyNumbering, No. 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MendelssohnSymphonyNumbering Context triple: [Symphony No. 1 in C minor, Op. 11, MendelssohnSymphonyNumbering, No. 1]
-
A.
numberOfSymphonies
Indicates the total count of symphonies associated with a given entity.
-
B.
workNumberInMahlerSymphonies
Indicates the specific numbered position a work occupies within the sequence of Mahler’s symphonies.
-
C.
workNumberInMozartSymphonies
Indicates the ordinal position or catalog number that a given work holds within the collection of Mozart’s symphonies.
-
D.
workNumberWithinLondonSymphonies
Indicates the numerical position or identifier assigned to a work within the set of London Symphonies.
-
E.
typicalMovementCountPerSymphony
Indicates the usual number of movements that a symphony typically contains.
- 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_69f348e463e08190b902d4819195e1f0 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6ab82b1248190b56f0d7e371b4368 |
completed | May 3, 2026, 1:57 a.m. |
| PD | Predicate disambiguation | batch_69f6aa21f2508190a204a424ffc00ca6 |
completed | May 3, 2026, 1:51 a.m. |
| PDg | Predicate description generation | batch_69f6aac95c1481909fff33702d0a6c37 |
completed | May 3, 2026, 1:54 a.m. |
Created at: April 30, 2026, 11:31 p.m.