Triple
T26692913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mario Party: The Top 100 |
E672936
|
entity |
| Predicate | playableCharactersInclude |
P43877
|
FINISHED |
| Object | Mario |
—
|
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: Mario | Statement: [Mario Party: The Top 100, playableCharactersInclude, Mario]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playableCharactersInclude Context triple: [Mario Party: The Top 100, playableCharactersInclude, Mario]
-
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.
playableCharacterFormOf
Indicates that one entity is a specific form or version of another entity as it appears as a playable character.
-
E.
featuresCharactersFrom
Indicates that one entity (such as a work or production) includes or presents characters originating from another entity.
- 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_69eecda2066c8190a344218afa5e89c1 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f61fd623bc819091df736cf3419b99 |
completed | May 2, 2026, 4:01 p.m. |
| PD | Predicate disambiguation | batch_69f61b3d23f481908dfec27adace900a |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 3:27 a.m.