Triple
T27879217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Impact World Championship |
E705040
|
entity |
| Predicate | winConditions |
P20842
|
FINISHED |
| Object | countout |
—
|
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: countout | Statement: [Impact World Championship, winConditions, countout]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: winConditions Context triple: [Impact World Championship, winConditions, countout]
-
A.
hasWinningCondition
Indicates that a particular condition or set of conditions determines when a participant, entity, or process is considered to have won or successfully completed a defined objective.
-
B.
conditionOfVictory
chosen
Indicates the specific circumstances or criteria under which a participant is considered to have won.
-
C.
winsFor
Indicates that one entity achieves victory or success on behalf of, or in favor of, another entity.
-
D.
pointsForWin
Indicates the number of points awarded to an entity for achieving a win in a given context or competition.
-
E.
winsDefinition
Indicates that one entity achieves victory or success over another in a contest, competition, or conflict.
- 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_69ef84111bb4819084298f994b31c62f |
completed | April 27, 2026, 3:43 p.m. |
| NER | Named-entity recognition | batch_69f63fd6c68481908c542aa03e297b9c |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6895f0819088655277e45859a8 |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 6:29 p.m.