Triple

T11542554
Position Surface form Disambiguated ID Type / Status
Subject Corrupted Blood incident E273708 entity
Predicate instanceOf P0 FINISHED
Object in-game event C1824 CONCEPT FINISHED

How this triple was built (1 step)

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.

CD Concept disambiguation gpt-5-mini-2025-08-07
Target class: in-game event
Context triple: [Corrupted Blood incident, instanceOf, in-game event]
  • A. event chosen
    An event is a distinct occurrence or happening, often bounded in time and space, that involves one or more participants and may trigger changes in state or behavior within a system.
  • B. seasonal event
    A seasonal event is a recurring occurrence or celebration that takes place during a specific time of year, often influenced by cultural, environmental, or climatic patterns.
  • C. esports arena
    An esports arena is a specialized venue designed and equipped to host competitive video gaming events, featuring professional-grade gaming setups, spectator seating, large display screens, and advanced audio-visual and networking infrastructure.
  • D. planned sports event
    A planned sports event is a scheduled and organized athletic competition or activity involving participants, rules, a set time and place, and often spectators.
  • E. event during basketball game
    An event during a basketball game is any discrete occurrence—such as a shot attempt, foul, turnover, substitution, or timeout—that changes the game state or is recorded in the game log.
  • F. None of above.

Provenance (1 batch)

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_69d6aae4dfa48190a3ab0b19a159a3c5 completed April 8, 2026, 7:22 p.m.
Created at: April 8, 2026, 9:37 p.m.