Triple
T30879714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haydn symphonies |
E786577
|
entity |
| Predicate | earliestSymphonies |
P178388
|
FINISHED |
| Object | early symphonies in three movements |
—
|
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: early symphonies in three movements | Statement: [Haydn symphonies, earliestSymphonies, early symphonies in three movements]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: earliestSymphonies Context triple: [Haydn symphonies, earliestSymphonies, early symphonies in three movements]
-
A.
numberOfSymphonies
Indicates the total count of symphonies associated with a given entity.
-
B.
earlyWorkOfComposer
chosen
Indicates that a work is among the earlier compositions created by a particular composer.
-
C.
oneOfLongestSymphonies
Indicates that the subject is among the longest symphonies in terms of duration or number of movements.
-
D.
firstConcertoComposed
Indicates that the subject is the first concerto ever composed by, or attributed to, the object.
-
E.
MendelssohnSymphonyNumbering
Indicates how Mendelssohn’s symphonies are assigned numbers, especially where publication order and composition order differ.
- 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_69f224bae17c8190bb3a6a28e3d019df |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f74062b9388190b30546cf700a825c |
completed | May 3, 2026, 12:32 p.m. |
| PD | Predicate disambiguation | batch_69f73c802b848190b61a416b7488bd96 |
completed | May 3, 2026, 12:16 p.m. |
Created at: April 29, 2026, 8:48 p.m.