Triple
T36851740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crash Bash |
E910691
|
entity |
| Predicate | minigameType |
P186584
|
FINISHED |
| Object | ball-bouncing games |
—
|
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: ball-bouncing games | Statement: [Crash Bash, minigameType, ball-bouncing games]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: minigameType Context triple: [Crash Bash, minigameType, ball-bouncing games]
-
A.
containsMinigame
Indicates that one entity includes or embeds a smaller, self-contained game within it.
-
B.
minigamesCount
Indicates the number of minigames associated with or contained within a given entity or context.
-
C.
minigameCountApprox
Indicates that the relationship expresses an approximate or estimated number of minigames associated with an entity.
-
D.
inGameType
Indicates that an entity participates in or belongs to a specific type or category within a game (e.g., game mode, classification, or role).
-
E.
minigamesSource
Indicates that one entity serves as the origin or provider of minigames for another entity.
- 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_69f76e8033d48190a59274f86f13be48 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f9fe1a1ca4819084c196f0041f0be2 |
completed | May 5, 2026, 2:26 p.m. |
| PD | Predicate disambiguation | batch_69f7cf7890008190a8bc355ff2d61c86 |
completed | May 3, 2026, 10:43 p.m. |
| PDg | Predicate description generation | batch_69f9fd66eed48190bdc26a8def328c2d |
completed | May 5, 2026, 2:23 p.m. |
Created at: May 3, 2026, 4:13 p.m.