Triple
T15578802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shellcreeper |
E374439
|
entity |
| Predicate | gameModeAppearance |
P69305
|
FINISHED |
| Object | single-player mode in Mario Bros. |
—
|
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: single-player mode in Mario Bros. | Statement: [Shellcreeper, gameModeAppearance, single-player mode in Mario Bros.]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameModeAppearance Context triple: [Shellcreeper, gameModeAppearance, single-player mode in Mario Bros.]
-
A.
appearsInGameMode
chosen
Indicates that an entity is present, available, or featured within a specified game mode.
-
B.
gameModeDesign
Indicates that one entity defines or specifies the rules, structure, or configuration of a particular game mode for another entity.
-
C.
gameModeRelevance
Indicates how strongly or in what way something is related or applicable to a particular game mode.
-
D.
primaryGameMode
Indicates the main or default game mode associated with a particular game or gaming context.
-
E.
introducedGameMode
Indicates that an entity caused a particular game mode to be created, revealed, or made available for use.
- 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_69d85ccd575081908909b71a3f3e3a61 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e24064c8190b132c3092877fbfa |
completed | April 16, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69deda817e9881909b0c66fc9056f7d5 |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:11 a.m.