Triple

T14271487
Position Surface form Disambiguated ID Type / Status
Subject Chase Center event service E353795 entity
Predicate operatesOnOccasion P37361 FINISHED
Object event days at Chase Center 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: event days at Chase Center | Statement: [Chase Center event service, operatesOnOccasion, event days at Chase Center]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: operatesOnOccasion
Context triple: [Chase Center event service, operatesOnOccasion, event days at Chase Center]
  • A. onOccasionOf
    Indicates that one event, action, or state occurs in connection with, or is triggered by, a particular occasion or special event.
  • B. usedOnOccasions chosen
    Indicates that something is employed or utilized during specific events, times, or circumstances rather than continuously.
  • C. createdOnOccasionOf
    Indicates that something was created specifically for, or in direct connection with, a particular event, occasion, or circumstance.
  • D. targetOccasion
    Indicates the specific event, situation, or occasion toward which an action, plan, or intention is directed.
  • E. suitableOccasion
    Indicates that a particular occasion or context is appropriate or fitting for a given entity, action, or event.
  • 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_69d8278d25148190abf1a8c8f5f533ad completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de65811d7c8190b075909a6570d415 completed April 14, 2026, 4:04 p.m.
PD Predicate disambiguation batch_69de2a7d586c8190846ff242bbf5ac53 completed April 14, 2026, 11:52 a.m.
Created at: April 10, 2026, 1:10 a.m.