Triple
T32945107
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sonic Origins Plus |
E842777
|
entity |
| Predicate | addsPlayableCharacter |
P43877
|
FINISHED |
| Object | Amy Rose |
—
|
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: Amy Rose | Statement: [Sonic Origins Plus, addsPlayableCharacter, Amy Rose]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: addsPlayableCharacter Context triple: [Sonic Origins Plus, addsPlayableCharacter, Amy Rose]
-
A.
hasPlayableCharacter
chosen
Indicates that an entity includes or is associated with a character that a user can control or play as.
-
B.
playableCharacterFormOf
Indicates that one entity is a specific form or version of another entity as it appears as a playable character.
-
C.
connectsCharacter
Indicates that one character is linked or associated with another in some meaningful way.
-
D.
numberOfPlayableCharacters
Indicates the total count of distinct characters that can be actively controlled or played by a user in a game or interactive experience.
-
E.
fictionalPlayer
Indicates that the referenced player entity is imaginary or does not exist in the real world, but is instead part of a fictional or simulated context.
- 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_69f34949727c81909d195c97de3341c8 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6d13fa5748190813ef184fcf2af41 |
completed | May 3, 2026, 4:38 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe5f93c8190995c53dbbe380a32 |
completed | May 3, 2026, 4:32 a.m. |
Created at: May 1, 2026, 1:20 a.m.