Triple
T2577161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Symphony No. 3 in E-flat major, Op. 55 "Eroica" |
E57003
|
entity |
| Predicate | translatedSubtitle |
P2765
|
FINISHED |
| Object | Heroic |
—
|
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: Heroic | Statement: [Symphony No. 3 in E-flat major, Op. 55 "Eroica", translatedSubtitle, Heroic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: translatedSubtitle Context triple: [Symphony No. 3 in E-flat major, Op. 55 "Eroica", translatedSubtitle, Heroic]
-
A.
subtitleDFunction
Indicates a functional relationship where one entity serves as the subtitle or secondary textual label for another entity.
-
B.
subtitle
chosen
Indicates that one work serves as a secondary or explanatory title to another, typically appearing beneath the main title.
-
C.
translationTargetLanguage
Indicates the language into which content is being or has been translated.
-
D.
translator
Indicates that one entity serves to convert or render content from one language or form into another for a second entity.
-
E.
titleInEnglish
Indicates that an entity’s title or name is given in the English language.
- 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_69ab4a4dca6481908c301f8e317396e7 |
completed | March 6, 2026, 9:42 p.m. |
| NER | Named-entity recognition | batch_69abd3a73a508190bf12e889a5d4bbf3 |
completed | March 7, 2026, 7:28 a.m. |
| PD | Predicate disambiguation | batch_69abd0cfeae08190aed03866ba071c5c |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:49 p.m.