Triple
T26092895
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bowser's Minions mode |
E658173
|
entity |
| Predicate | playableCharacters |
P43877
|
FINISHED |
| Object | Koopa Troopas |
E228541
|
NE 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: Koopa Troopas | Statement: [Bowser's Minions mode, playableCharacters, Koopa Troopas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playableCharacters Context triple: [Bowser's Minions mode, playableCharacters, Koopa Troopas]
-
A.
hasPlayableCharacter
chosen
Indicates that an entity includes or is associated with a character that a user can control or play as.
-
B.
characterInPlayBy
Indicates that a character appears in or is part of a play authored or created by a specific person.
-
C.
numberOfPlayableCharacters
Indicates the total count of distinct characters that can be actively controlled or played by a user in a game or interactive experience.
-
D.
featuresCharactersFrom
Indicates that one entity (such as a work or production) includes or presents characters originating from another entity.
-
E.
associatedCharacters
Indicates that two or more characters are linked or connected through some relationship, involvement, or relevance to each other.
- F. None of above.
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_69ee5bbfc4d08190a1b206d0ac3a1e8d |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f607335d60819081808e1a52941262 |
completed | May 2, 2026, 2:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a11274ac0608190a601b3211ebc6e1e |
completed | May 23, 2026, 4:04 a.m. |
| PD | Predicate disambiguation | batch_69f602d07590819085ac34b189613104 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 26, 2026, 7:48 p.m.