Triple
T25433492
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Domineering |
E637317
|
entity |
| Predicate | hasWinningCondition |
P158834
|
FINISHED |
| Object | last player to make a legal move wins |
—
|
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 make a legal move wins | Statement: [Domineering, hasWinningCondition, last player to make a legal move wins]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWinningCondition Context triple: [Domineering, hasWinningCondition, last player to make a legal move wins]
-
A.
hasWinningScore
Indicates that one entity possesses a score that is sufficient to win in a given competition, game, or scoring context.
-
B.
hasWinnerType
Indicates that an entity has a specific type or category of winner associated with it.
-
C.
hasWinners
Indicates that an event, competition, or context has one or more entities designated as winners.
-
D.
winnerState
Indicates the state or condition of an entity that has achieved victory or been declared the winner in a given context.
-
E.
canBeWonWithout
Indicates that a goal, contest, or outcome can be successfully achieved without the involvement, use, or occurrence of a specified entity or condition.
- 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_69e75db6c97081908178383fa632b193 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f5f6dd99f88190848a5bbee795aa17 |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f4806d93dc8190b9dff4c63186faff |
completed | May 1, 2026, 10:29 a.m. |
| PDg | Predicate description generation | batch_69f48b9058d081908ec9af261ee092e2 |
completed | May 1, 2026, 11:16 a.m. |
Created at: April 21, 2026, 1:59 p.m.