Triple

T1483943
Position Surface form Disambiguated ID Type / Status
Subject Conway’s Game of Sprouts E29420 entity
Predicate winningCondition P20842 FINISHED
Object last player to move wins under normal play 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: last player to move wins under normal play | Statement: [Conway’s Game of Sprouts, winningCondition, last player to move wins under normal play]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: winningCondition
Context triple: [Conway’s Game of Sprouts, winningCondition, last player to move wins under normal play]
  • A. conditionOfVictory chosen
    Indicates the specific circumstances or criteria under which a participant is considered to have won.
  • B. winnerState
    Indicates the state or condition of an entity that has achieved victory or been declared the winner in a given context.
  • C. pointsForWin
    Indicates the number of points awarded to an entity for achieving a win in a given context or competition.
  • D. winnerThrows
    Indicates that the entity identified as the winner performs or executes a throw action toward or involving another entity.
  • E. decidingGameWinner
    Indicates that an event, action, or process determines which participant is the winner of a game.
  • 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_69a498da82e08190ba833330d05f380f completed March 1, 2026, 7:51 p.m.
NER Named-entity recognition batch_69a4c679714c8190ac53630fb49e19c5 completed March 1, 2026, 11:06 p.m.
PD Predicate disambiguation batch_69a4c486eacc81909c272f9bdf50a7c3 completed March 1, 2026, 10:58 p.m.
Created at: March 1, 2026, 8:12 p.m.