Triple

T1562022
Position Surface form Disambiguated ID Type / Status
Subject University of Oklahoma E33346 entity
Predicate nickname P55 FINISHED
Object OU E177505 NE 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: OU | Statement: [University of Oklahoma, nickname, OU]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: OU
Context triple: [University of Oklahoma, nickname, OU]
  • A. OU chosen
    OU is a major public research university located in Norman, Oklahoma, known for its strong academic programs and prominent athletics, especially college football.
  • B. UA
    UA is a major public research university located in Tucson, Arizona, known for its strong programs in astronomy, space sciences, and environmental studies.
  • C. UA
    UA is the two-letter IATA airline designator used worldwide to identify United Airlines on tickets, schedules, and flight information.
  • D. UA
    UA is the two-letter ISO 3166-1 alpha-2 country code assigned to Ukraine for international standardization and identification purposes.
  • E. UA
    UA is a major public research university located in Tuscaloosa, Alabama, known for its strong academic programs and prominent Crimson Tide athletics.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69a885ef9cf48190b0af0f5ce3d02231 completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69a908886efc8190a630ef1e06d0d9cb completed March 5, 2026, 4:37 a.m.
NED1 Entity disambiguation (via context triple) batch_69ad40217be88190ae17abcf1541ec55 completed March 8, 2026, 9:23 a.m.
Created at: March 4, 2026, 7:27 p.m.