Triple
T29022978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sonic Colors |
E737505
|
entity |
| Predicate | usesPowerUp |
P172330
|
FINISHED |
| Object | White Wisp |
—
|
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: White Wisp | Statement: [Sonic Colors, usesPowerUp, White Wisp]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesPowerUp Context triple: [Sonic Colors, usesPowerUp, White Wisp]
-
A.
powerUp
Indicates an action where an entity increases or restores another entity’s energy, strength, or functional capacity.
-
B.
usesPowerFor
Indicates that one entity applies or exploits a particular power, energy, or capability for a specific purpose or activity.
-
C.
hasPowerUpItem
chosen
Indicates that an entity possesses or is currently benefiting from a power-up item.
-
D.
usesPowerType
Indicates that one entity operates or functions by means of a specified type or source of power.
-
E.
powerUpBehavior
Indicates how an entity changes state or acts when it gains a power-up or temporary enhancement.
- 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_69f077ee19f881909af48f9cab00a2e5 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6d0d46aec819091edf97324d793ac |
completed | May 3, 2026, 4:36 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe2183481908ae4e85a59c66f69 |
completed | May 3, 2026, 4:32 a.m. |
Created at: April 28, 2026, 9:50 a.m.