Triple

T2511013
Position Surface form Disambiguated ID Type / Status
Subject Aggie War Hymn E52698 entity
Predicate traditionallySungBy P32287 FINISHED
Object students 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: students | Statement: [Aggie War Hymn, traditionallySungBy, students]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: traditionallySungBy
Context triple: [Aggie War Hymn, traditionallySungBy, students]
  • A. isTraditionallySungBy chosen
    Indicates that something, typically a song or chant, is customarily performed vocally by a particular person, group, or type of performer according to tradition.
  • B. sungAs
    Indicates that something is performed or vocalized in the manner, role, or identity specified by another entity (e.g., a song or part being sung as a particular character, style, or version).
  • C. includesTraditionalSong
    Indicates that one entity contains or features a traditional song as part of its content or composition.
  • D. performedAsSingerIn
    Indicates that an entity took part in a performance specifically in the role of a singer within a particular event, production, or context.
  • E. performedSongFor
    Indicates that one entity performed a song specifically for another entity as the intended audience or recipient.
  • 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_69ab4958e76481908a235377dd921c9e completed March 6, 2026, 9:38 p.m.
NER Named-entity recognition batch_69abd5a33234819082ad49fa6594b6be completed March 7, 2026, 7:37 a.m.
PD Predicate disambiguation batch_69abd0bf37c0819088d28b5081ba7556 completed March 7, 2026, 7:16 a.m.
Created at: March 6, 2026, 9:46 p.m.