Triple
T21570251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WorldWinner |
E532263
|
entity |
| Predicate | gameplayBasis |
P144292
|
FINISHED |
| Object | skill |
—
|
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: skill | Statement: [WorldWinner, gameplayBasis, skill]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameplayBasis Context triple: [WorldWinner, gameplayBasis, skill]
-
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.
basedOnPlayBy
Indicates that something (typically a creative work) is derived or adapted from a play authored by a specified entity.
-
C.
gameplayImpact
Indicates how one element in a game affects the mechanics, difficulty, or overall experience of playing that game.
-
D.
primaryGameType
Indicates the main category or type of game with which an entity is primarily associated.
-
E.
ballGameType
Indicates the specific kind or category of ball game associated with an event or activity.
- 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_69e0c460db088190828c64206a450273 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eee9cc5c448190887a836f577d01ba |
completed | April 27, 2026, 4:45 a.m. |
| PD | Predicate disambiguation | batch_69e6320c8c2c81908bf031447d66a052 |
completed | April 20, 2026, 2:02 p.m. |
| PDg | Predicate description generation | batch_69e633bf34c481909925d8dc1a633a65 |
completed | April 20, 2026, 2:10 p.m. |
Created at: April 16, 2026, 6:30 p.m.