Triple
T13148568
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Donut Plains |
E312402
|
entity |
| Predicate | introducedPowerUp |
P48191
|
FINISHED |
| Object | Cape Feather |
—
|
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: Cape Feather | Statement: [Donut Plains, introducedPowerUp, Cape Feather]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedPowerUp Context triple: [Donut Plains, introducedPowerUp, Cape Feather]
-
A.
powerUp
Indicates an action where an entity increases or restores another entity’s energy, strength, or functional capacity.
-
B.
featuresNewPowerUps
chosen
Indicates that something includes or introduces newly added power-up abilities or items.
-
C.
powerUpBehavior
Indicates how an entity changes state or acts when it gains a power-up or temporary enhancement.
-
D.
gainedPowerAfter
Indicates that one entity acquired power, authority, or influence subsequent to an event, condition, or action involving another entity.
-
E.
canBePoweredUp
Indicates that an entity has the capability to receive additional power or energy, enhancing its state or functionality.
- 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_69d806aabde48190899e13e41659cae5 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bbd1d088190b7c69f37fc6eeb64 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:11 p.m.