Triple
T11250300
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rage |
E266305
|
entity |
| Predicate | containsMiniGame |
P85924
|
FINISHED |
| Object | card game |
—
|
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: card game | Statement: [Rage, containsMiniGame, card game]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsMiniGame Context triple: [Rage, containsMiniGame, card game]
-
A.
containsMinigame
chosen
Indicates that one entity includes or embeds a smaller, self-contained game within it.
-
B.
addsMinigames
Indicates that an entity introduces or incorporates additional minigames into another entity, such as a game, system, or platform.
-
C.
hasShortGameArea
Indicates that an entity includes or is associated with a designated short-game practice area (e.g., for chipping, pitching, or putting).
-
D.
playableInGame
Indicates that something can be used or controlled as an active element within a particular game.
-
E.
hasSpecialGames
Indicates that an entity is associated with particular games that are distinguished from its regular or standard games in some special way.
- 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_69d6aac7953c8190b82caf9d7640fdf9 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e93212448190b46b3799b0bdfa0f |
completed | April 9, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69d78793c00481908a3f764b610b77a4 |
completed | April 9, 2026, 11:03 a.m. |
Created at: April 8, 2026, 9:31 p.m.