Triple

T6852182
Position Surface form Disambiguated ID Type / Status
Subject Paycor Stadium E158045 entity
Predicate namingRightsPartner P3318 FINISHED
Object Paycor, Inc. E624004 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: Paycor, Inc. | Statement: [Paycor Stadium, namingRightsPartner, Paycor, Inc.]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Paycor, Inc.
Context triple: [Paycor Stadium, namingRightsPartner, Paycor, Inc.]
  • A. Paycor, Inc. chosen
    Paycor, Inc. is a U.S.-based provider of human capital management and payroll software solutions for small and midsize businesses.
  • B. Paychex
    Paychex is a leading American provider of payroll, human resources, and benefits outsourcing services for small to mid-sized businesses.
  • C. Paylocity
    Paylocity is a U.S.-based provider of cloud payroll and human capital management software solutions for businesses.
  • D. Square Payroll
    Square Payroll is a cloud-based payroll service designed for small and medium-sized businesses to manage employee and contractor payments, tax filings, and compliance.
  • E. Paycom
    Paycom is a U.S.-based software company that provides cloud-based payroll and human capital management solutions to businesses.
  • 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_69c6882fae988190864cbba788c5ebb4 completed March 27, 2026, 1:37 p.m.
NER Named-entity recognition batch_69c6d84e6fb08190915954be5b0df2d8 completed March 27, 2026, 7:19 p.m.
NED1 Entity disambiguation (via context triple) batch_69c7427dda908190953cf8b535249980 completed March 28, 2026, 2:52 a.m.
Created at: March 27, 2026, 2:20 p.m.