Triple

T18215633
Position Surface form Disambiguated ID Type / Status
Subject UCLA later defeated Houston in the 1968 NCAA Final Four rematch E436147 entity
Predicate instanceOf P0 FINISHED
Object basketball game outcome C39903 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: basketball game outcome
Context triple: [UCLA later defeated Houston in the 1968 NCAA Final Four rematch, instanceOf, basketball game outcome]
  • A. 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.
  • B. basketball video game
    A basketball video game is an interactive digital simulation that lets players control teams or individual athletes to compete in virtual basketball matches, often featuring realistic physics, official leagues, and various gameplay modes.
  • C. basketball exhibition game
    A basketball exhibition game is a non-competitive or unofficial matchup, often used for entertainment, practice, fundraising, or promotional purposes rather than for league standings or championships.
  • D. professional basketball game
    A professional basketball game is a competitive sporting event in which organized teams of elite players follow official basketball rules to score points by shooting a ball through the opponent’s hoop within a set time.
  • E. basketball court
    A basketball court is a rectangular playing surface marked with boundary lines, a center circle, free-throw lanes, and three-point arcs, featuring two opposing baskets where the game of basketball is played.
  • F. None of above. chosen

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_69d8b9103a8081908bbb0836fef10efd completed April 10, 2026, 8:47 a.m.
Created at: April 10, 2026, 10:32 a.m.