Triple

T23673990
Position Surface form Disambiguated ID Type / Status
Subject 2012 NCAA Division I men's basketball tournament E584815 entity
Predicate playInVenue P96050 FINISHED
Object University of Dayton Arena NE NERFINISHED

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: University of Dayton Arena | Statement: [2012 NCAA Division I men's basketball tournament, playInVenue, University of Dayton Arena]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: playInVenue
Context triple: [2012 NCAA Division I men's basketball tournament, playInVenue, University of Dayton Arena]
  • A. intendedPerformanceVenue
    Indicates the venue or location where a performance is planned or intended to take place.
  • B. locatedInVenueType
    Indicates that an entity is situated within or associated with a venue of a specific type (e.g., stadium, theater, restaurant).
  • C. performedAtVenue chosen
    Indicates that an event or performance took place at a specific venue or location.
  • D. hasVenueFor
    Indicates that one entity provides or serves as the location or setting where an event, activity, or function takes place for another entity.
  • E. locatedInOperatedVenue
    Indicates that an entity is situated within a venue that is managed or operated by a specified agent or organization.
  • 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_69e24901421881908c17a5293bdd4a8e completed April 17, 2026, 2:51 p.m.
NER Named-entity recognition batch_69f1b4f1dee08190bfe78564c65f01ad completed April 29, 2026, 7:36 a.m.
PD Predicate disambiguation batch_69f118dd13008190a8799b4e9cadbd79 completed April 28, 2026, 8:30 p.m.
Created at: April 17, 2026, 6:51 p.m.