Triple
T29360487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sonic Forces |
E744574
|
entity |
| Predicate | supportsCharacterCreation |
P197997
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Sonic Forces, supportsCharacterCreation, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsCharacterCreation Context triple: [Sonic Forces, supportsCharacterCreation, true]
-
A.
hasCharacterCreation
chosen
Indicates that an entity includes or supports a process for creating or customizing characters.
-
B.
hasCreatedCharacterFor
Indicates that one entity has created or designed a character specifically for another entity or context.
-
C.
supportedByCharacter
Indicates that an entity receives backing, assistance, or endorsement from a specific character.
-
D.
supportCharacter
Indicates that one entity provides assistance, backing, or reinforcement to another entity in performing an action or fulfilling a role.
-
E.
supportedCreationOf
Indicates that one entity actively aided, endorsed, or facilitated the bringing into existence or establishment of 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_69f0a79aee588190b490f19d93c6e52d |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_6a032616547c8190bc877202e43403eb |
completed | May 12, 2026, 1:07 p.m. |
| PD | Predicate disambiguation | batch_6a0325246abc819088e16a7fbadf40c5 |
completed | May 12, 2026, 1:03 p.m. |
Created at: April 28, 2026, 2:17 p.m.