Triple
T15466007
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boomerang Flower |
E372031
|
entity |
| Predicate | powerUpType |
P108777
|
FINISHED |
| Object | offensive power-up |
—
|
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: offensive power-up | Statement: [Boomerang Flower, powerUpType, offensive power-up]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: powerUpType Context triple: [Boomerang Flower, powerUpType, offensive power-up]
-
A.
powerUp
Indicates an action where an entity increases or restores another entity’s energy, strength, or functional capacity.
-
B.
powerUpBehavior
Indicates how an entity changes state or acts when it gains a power-up or temporary enhancement.
-
C.
canBePoweredUp
Indicates that an entity has the capability to receive additional power or energy, enhancing its state or functionality.
-
D.
featuresPowerUp
chosen
Indicates that one entity includes, provides, or incorporates a power-up as part of its content or functionality.
-
E.
enhancesPowersOf
Indicates that one entity increases, amplifies, or strengthens the abilities or powers 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_69d85cc8bd308190886949510b42e764 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f680cec8190836a5ec841dee224 |
completed | April 16, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69ded284bd008190b31c53b4f1cebadd |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:33 a.m.