Triple

T37501525
Position Surface form Disambiguated ID Type / Status
Subject The Generation Game E931974 entity
Predicate typicalRound P205930 FINISHED
Object conveyor belt memory game 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: conveyor belt memory game | Statement: [The Generation Game, typicalRound, conveyor belt memory game]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typicalRound
Context triple: [The Generation Game, typicalRound, conveyor belt memory game]
  • A. typicalGame
    Indicates a relationship where one entity is characterized as a standard, representative, or commonly occurring example of a game for the other entity or context.
  • B. standardRoundLength
    Indicates that there is a defined, typical duration assigned to a single round within a process, activity, or game.
  • C. standardServiceRoundOf
    Indicates that one entity is the standard or typical service round associated with another entity (such as a process, schedule, or service context).
  • D. reachedRound
    Indicates that an entity has advanced to or attained a particular round or stage within a process, event, or competition.
  • E. roundOf
    Indicates that one event, match, or game occurs as a specific stage or phase within a larger competition or tournament.
  • F. None of above. chosen

Provenance (4 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_69f76ec5268481909ea01c73aeeefd42 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_6a037cad051c8190b28b354b89208574 completed May 12, 2026, 7:17 p.m.
PD Predicate disambiguation batch_6a037a1553e08190bb7424c448cb1f33 completed May 12, 2026, 7:05 p.m.
PDg Predicate description generation batch_6a037c842b2c819082f1d2db995ac2eb completed May 12, 2026, 7:16 p.m.
Created at: May 3, 2026, 4:17 p.m.