Triple
T37649838
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Akito |
E937141
|
entity |
| Predicate | usesElementalPower |
P47735
|
FINISHED |
| Object | wind-based attacks |
—
|
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: wind-based attacks | Statement: [Akito, usesElementalPower, wind-based attacks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesElementalPower Context triple: [Akito, usesElementalPower, wind-based attacks]
-
A.
elementalPower
Indicates a relationship where an entity possesses, controls, or is associated with a specific elemental force or power.
-
B.
hasRoleInElementals
Indicates that an entity holds a specific role or function within a group, system, or context referred to as "Elementals".
-
C.
usesPowerType
chosen
Indicates that one entity operates or functions by means of a specified type or source of power.
-
D.
usesPowerFor
Indicates that one entity applies or exploits a particular power, energy, or capability for a specific purpose or activity.
-
E.
hasHeroPower
Indicates that one entity possesses or is endowed with a special ability or power characteristic of a hero in relation to 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_69f76ed4fe908190b8061c5c135e0971 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd166a488190b1bf9316b0790801 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:18 p.m.