Triple
T10006626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eat My Dust |
E198267
|
entity |
| Predicate | hasGameplayFeature |
P8300
|
FINISHED |
| Object | competitive gameplay |
—
|
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: competitive gameplay | Statement: [Eat My Dust, hasGameplayFeature, competitive gameplay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGameplayFeature Context triple: [Eat My Dust, hasGameplayFeature, competitive gameplay]
-
A.
featuresGame
Indicates that something (such as a platform, service, or collection) includes or presents a particular game as part of its offerings.
-
B.
hasFunctionInGames
Indicates that something serves a specific role, purpose, or function within the context of games.
-
C.
hasFeatureCode
Indicates that an entity is associated with a specific feature identifier or code that characterizes one of its properties or attributes.
-
D.
hasGameType
chosen
Indicates that an entity (such as a game or match) is associated with a specific category or type of game.
-
E.
hasPlayType
Indicates the type or category of play associated with an event, action, or performance.
- 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_69ca830fcca48190bbbd9b20c233835f |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cdcd16afb481909a5d5893e024683f |
completed | April 2, 2026, 1:57 a.m. |
| PD | Predicate disambiguation | batch_69cd1da2cf9081908a6c0eb5247d0bc2 |
completed | April 1, 2026, 1:29 p.m. |
Created at: March 30, 2026, 8:51 p.m.