Triple
T25925949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Super Mario Maker |
E653303
|
entity |
| Predicate | supportsGameStyle |
P192035
|
FINISHED |
| Object | Super Mario Bros. |
—
|
NE NERFINISHED |
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: Super Mario Bros. | Statement: [Super Mario Maker, supportsGameStyle, Super Mario Bros.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsGameStyle Context triple: [Super Mario Maker, supportsGameStyle, Super Mario Bros.]
-
A.
supportsGames
Indicates that an entity is capable of running, handling, or being compatible with one or more games.
-
B.
supportsGameEngine
Indicates that one entity provides compatibility, functionality, or resources necessary for the operation or integration of a particular game engine.
-
C.
includesGameType
Indicates that one entity contains or supports a particular type or category of game.
-
D.
hasGameType
Indicates that an entity (such as a game or match) is associated with a specific category or type of game.
-
E.
supportsGameStreaming
Indicates that one entity provides the capability for another entity to stream and play games remotely in real time.
- 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_69e7ab3eb9b881909c1390690551f868 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69fcf36bb86c8190a0a0ccf47cb56e5c |
completed | May 7, 2026, 8:17 p.m. |
Created at: April 22, 2026, 8:35 a.m.