Triple

T37611357
Position Surface form Disambiguated ID Type / Status
Subject Akademische Festouvertüre E935791 entity
Predicate hasClosingCharacter P196031 FINISHED
Object triumphant 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: triumphant | Statement: [Akademische Festouvertüre, hasClosingCharacter, triumphant]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasClosingCharacter
Context triple: [Akademische Festouvertüre, hasClosingCharacter, triumphant]
  • A. hasClosingSectionCharacter
    Indicates that something includes a specific character used to mark the end of a section.
  • B. hasClosingAction
    Indicates that an entity performs or is associated with an action that brings a process, event, or interaction to an end.
  • C. hasClosingMotif
    Indicates that one entity features or is associated with a recurring thematic or structural pattern used at the end or conclusion of another entity.
  • D. hasEnding
    Indicates that one entity concludes with, or terminates in, another entity (such as a specific substring, segment, or final component).
  • E. closingSectionCharacter
    Indicates that one character functions as the closing or terminating symbol for a particular section or block of content in relation to another element.
  • F. None of above. chosen

Provenance (4 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_69f76ed0a85481909254a8a89090c826 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fe00dad1708190b6522476bebb43af completed May 8, 2026, 3:27 p.m.
PD Predicate disambiguation batch_69fdfc3717f48190bb50ac2919c8ef95 completed May 8, 2026, 3:07 p.m.
PDg Predicate description generation batch_69fe00d8d8248190a63c12aa2c2f7c0c completed May 8, 2026, 3:27 p.m.
Created at: May 3, 2026, 4:18 p.m.