Triple
T25803455
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mario Party 3 |
E649898
|
entity |
| Predicate | notableMiniGameType |
P186584
|
FINISHED |
| Object | 4-player mini-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: 4-player mini-games | Statement: [Mario Party 3, notableMiniGameType, 4-player mini-games]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableMiniGameType Context triple: [Mario Party 3, notableMiniGameType, 4-player mini-games]
-
A.
notableGameType
Indicates that a game is of a particular type or category for which the subject is especially well known or notable.
-
B.
minigameType
chosen
Indicates the specific category or kind of minigame associated with an entity or event.
-
C.
notableBuiltInGame
Indicates that an entity is a well-known or significant game that is pre-installed or comes bundled by default within another product or platform.
-
D.
notableGame
Indicates that a particular game is especially significant, prominent, or well-known in relation to the associated entity.
-
E.
containsMinigame
Indicates that one entity includes or embeds a smaller, self-contained game within it.
- 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_69e7ab34f8c8819099f6c4dabdabf129 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69fda5003cdc8190a558501271389912 |
completed | May 8, 2026, 8:55 a.m. |
| PD | Predicate disambiguation | batch_69fda05bfc2c819096821a5300e9bb24 |
completed | May 8, 2026, 8:35 a.m. |
Created at: April 22, 2026, 6:43 a.m.