Triple
T11659469
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Elytra |
E277085
|
entity |
| Predicate | boostEffect |
P82640
|
FINISHED |
| Object | increases speed while gliding |
—
|
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: increases speed while gliding | Statement: [Elytra, boostEffect, increases speed while gliding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boostEffect Context triple: [Elytra, boostEffect, increases speed while gliding]
-
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.
enhancesPowersOf
chosen
Indicates that one entity increases, amplifies, or strengthens the abilities or powers of another entity.
-
D.
heroPowerEffect
Indicates the specific impact or outcome that a hero’s power has when it is used.
-
E.
tierEffect
Indicates how belonging to a particular tier influences or modifies the outcome, behavior, or properties associated with that tier.
- 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_69d6aafbb3c081908a9cdb4ecb8d981d |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a3d19c788190826d849a6ffedc72 |
completed | April 10, 2026, 7:16 a.m. |
| PD | Predicate disambiguation | batch_69d88a73f9ac819095662042804bf40a |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:39 p.m.