Triple

T6615945
Position Surface form Disambiguated ID Type / Status
Subject Brigham Young Cougars football team E149350 entity
Predicate offensiveIdentity P25454 FINISHED
Object pass-oriented offense 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: pass-oriented offense | Statement: [Brigham Young Cougars football team, offensiveIdentity, pass-oriented offense]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: offensiveIdentity
Context triple: [Brigham Young Cougars football team, offensiveIdentity, pass-oriented offense]
  • A. offenseNicknamed
    Indicates that an offensive unit, team, or strategy is commonly referred to by a particular nickname.
  • B. usedOffensiveSystem
    Indicates that an entity employed an offensive system (such as a weapon or attack mechanism) against another entity or target.
  • C. offense
    Indicates that one entity commits, causes, or is responsible for a violation, wrongdoing, or rule-breaking act against another entity or governing norms.
  • D. offensiveStrategy chosen
    Indicates a strategic approach focused on attacking or aggressively advancing against an opponent.
  • E. insultedAs
    Indicates that one entity directed an insulting or offensive remark or action toward another entity, characterizing the target in a demeaning way.
  • 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_69c687ebc680819094caf71faba2efe2 completed March 27, 2026, 1:36 p.m.
NER Named-entity recognition batch_69c6bdb88cc881908f35648c15a7dc85 completed March 27, 2026, 5:26 p.m.
PD Predicate disambiguation batch_69c6ad007c1c8190af425f51011c7ad1 completed March 27, 2026, 4:14 p.m.
Created at: March 27, 2026, 1:57 p.m.