Triple
T2577173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Symphony No. 3 in E-flat major, Op. 55 "Eroica" |
E57003
|
entity |
| Predicate | approximateCompositionEnd |
P35259
|
FINISHED |
| Object | 1804 |
—
|
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: 1804 | Statement: [Symphony No. 3 in E-flat major, Op. 55 "Eroica", approximateCompositionEnd, 1804]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateCompositionEnd Context triple: [Symphony No. 3 in E-flat major, Op. 55 "Eroica", approximateCompositionEnd, 1804]
-
A.
hasApproximateEnd
Indicates that an entity’s end point, time, or boundary is known only approximately rather than precisely.
-
B.
timePeriodEndApprox
chosen
Indicates that the associated time period ends at an approximate, rather than exact, point in time.
-
C.
hasApproximateDuration
Indicates that one entity has a duration that is estimated or not exact, typically expressed as an approximate length of time.
-
D.
notablePositionEnd
Indicates the point in time or event at which an entity’s notable position, role, or office comes to an end.
-
E.
hasEnding
Indicates that one entity concludes with, or terminates in, another entity (such as a specific substring, segment, or final component).
- 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.