Triple

T13871177
Position Surface form Disambiguated ID Type / Status
Subject Rumble the Bison E333452 entity
Predicate homeVenue P105 FINISHED
Object Paycom Center E171338 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: Paycom Center | Statement: [Rumble the Bison, homeVenue, Paycom Center]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Paycom Center
Context triple: [Rumble the Bison, homeVenue, Paycom Center]
  • A. Paycom Center chosen
    Paycom Center is a multi-purpose indoor arena in downtown Oklahoma City best known as the home of the NBA’s Oklahoma City Thunder.
  • B. Paycom
    Paycom is a U.S.-based software company that provides cloud-based payroll and human capital management solutions to businesses.
  • C. Paylocity
    Paylocity is a U.S.-based provider of cloud payroll and human capital management software solutions for businesses.
  • D. Paychex
    Paychex is a leading American provider of payroll, human resources, and benefits outsourcing services for small to mid-sized businesses.
  • E. AccuWage Online
    AccuWage Online is a web-based tool from the U.S. Social Security Administration that allows employers to test and validate their wage report files before submitting them electronically.
  • 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_69d81c5ced9c8190b0e9bcc6effe5959 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de05c638248190bbe5d19f7b88d0f9 completed April 14, 2026, 9:15 a.m.
NED1 Entity disambiguation (via context triple) batch_69f7c107c20c81909dff0ca4a59fcc55 completed May 3, 2026, 9:41 p.m.
Created at: April 9, 2026, 10:14 p.m.