Triple
T22878773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Christmas Concerto |
E567398
|
entity |
| Predicate | finaleTitle |
P128609
|
FINISHED |
| Object | Pastorale ad libitum |
—
|
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: Pastorale ad libitum | Statement: [Christmas Concerto, finaleTitle, Pastorale ad libitum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finaleTitle Context triple: [Christmas Concerto, finaleTitle, Pastorale ad libitum]
-
A.
hasFinale
chosen
Indicates that one entity serves as the concluding or final part (such as an ending segment, episode, or event) of another entity.
-
B.
laterFinale
Indicates that one event, episode, or occurrence serves as a concluding part that happens after another referenced event or finale.
-
C.
finalAct
Indicates that an action or event is the last or concluding act in a sequence or process.
-
D.
originalFinale
Indicates that something serves as the initial or authentic concluding part or ending of another work, event, or sequence.
-
E.
finalFilmBy
Indicates that a given film is the last movie directed, produced, or otherwise primarily created by a particular person or entity in their career or filmography.
- 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_69e24589d8348190b96422d13a678bc1 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17f5a26f4819086ede6d85a2ab2bf |
completed | April 29, 2026, 3:47 a.m. |
| PD | Predicate disambiguation | batch_69ef3b6b2e2481908258156937b5a745 |
completed | April 27, 2026, 10:33 a.m. |
Created at: April 17, 2026, 3:39 p.m.