Triple

T16330719
Position Surface form Disambiguated ID Type / Status
Subject Mike Gundy E396542 entity
Predicate primaryOffensiveScheme P25454 FINISHED
Object spread 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: spread offense | Statement: [Mike Gundy, primaryOffensiveScheme, spread offense]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: primaryOffensiveScheme
Context triple: [Mike Gundy, primaryOffensiveScheme, spread offense]
  • A. offensiveStrategy chosen
    Indicates a strategic approach focused on attacking or aggressively advancing against an opponent.
  • B. offensiveSchemeHistory
    Indicates a relationship where an entity’s past or previously used offensive schemes, strategies, or play systems are recorded or associated with it over time.
  • C. offensiveStrength
    Indicates the degree or capacity of an entity to carry out effective attacks or aggressive actions against an opponent.
  • D. offensiveCoordinator
    Indicates that one entity serves as the offensive coordinator (the coach responsible for directing the offensive unit) for another entity, typically a sports team.
  • E. offensiveTackle
    Indicates that an entity plays the offensive tackle position, responsible for blocking and protecting on the offensive line in a gridiron football context.
  • 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_69d87f255b788190a400eba031dd85d8 completed April 10, 2026, 4:40 a.m.
NER Named-entity recognition batch_69e2c4debef08190a64f13214bfa098f completed April 17, 2026, 11:40 p.m.
PD Predicate disambiguation batch_69e226eba9b48190af6e80d3d1c2aed3 completed April 17, 2026, 12:26 p.m.
Created at: April 10, 2026, 5:07 a.m.