Triple
T36209421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Symphony No. 1 in E major, Op. 26 |
E1047495
|
entity |
| Predicate | finaleType |
P128609
|
FINISHED |
| Object | choral finale |
—
|
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: choral finale | Statement: [Symphony No. 1 in E major, Op. 26, finaleType, choral finale]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finaleType Context triple: [Symphony No. 1 in E major, Op. 26, finaleType, choral finale]
-
A.
finalMatchType
Indicates the specific category or format of the concluding or decisive match in a series or competition.
-
B.
hasFinale
chosen
Indicates that one entity serves as the concluding or final part (such as an ending segment, episode, or event) of another entity.
-
C.
grandFinalGroundType
Indicates the type or category of ground surface on which a grand final event is held.
-
D.
finishType
Indicates the manner or outcome by which an action, process, or event is completed.
-
E.
isFinalsOf
Indicates that one entity represents the final or concluding stage, round, or version of another entity.
- 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_69f76e4214748190a76c986d2a1838c2 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69feced53a7c819098ec474fb7d514b0 |
completed | May 9, 2026, 6:06 a.m. |
| PD | Predicate disambiguation | batch_69fecd9cd5288190aac8b4e04a7ee78e |
completed | May 9, 2026, 6:01 a.m. |
Created at: May 3, 2026, 4:09 p.m.