Triple

T82870
Position Surface form Disambiguated ID Type / Status
Subject United Center E1664 entity
Predicate hasClubSeating P2608 FINISHED
Object yes 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: yes | Statement: [United Center, hasClubSeating, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasClubSeating
Context triple: [United Center, hasClubSeating, yes]
  • A. hasSeating chosen
    Indicates that one entity provides or contains seating capacity or seating arrangements for another entity.
  • B. seatingCapacity
    Indicates the maximum number of people that something (typically a venue or vehicle) is designed or allowed to seat.
  • C. seatingAddedYear
    Indicates the year in which additional seating was installed or added to a venue or location.
  • D. familySeat
    Indicates the traditional principal residence or ancestral home associated with a particular family or lineage.
  • E. hasCabinClass
    Indicates that an entity (such as a booking, ticket, or seat) is associated with a specific cabin class (e.g., economy, business, first).
  • 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_69a24c8150408190910a693eb51c1f71 completed Feb. 28, 2026, 2:01 a.m.
NER Named-entity recognition batch_69a25053ca208190a371b0d38000c2b9 completed Feb. 28, 2026, 2:17 a.m.
PD Predicate disambiguation batch_69a24eb2998c819082681da74601d446 completed Feb. 28, 2026, 2:10 a.m.
Created at: Feb. 28, 2026, 2:06 a.m.