Triple
T28901464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neon |
E732960
|
entity |
| Predicate | ultimateAbilityType |
P47735
|
FINISHED |
| Object | high-damage electric beam |
—
|
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: high-damage electric beam | Statement: [Neon, ultimateAbilityType, high-damage electric beam]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ultimateAbilityType Context triple: [Neon, ultimateAbilityType, high-damage electric beam]
-
A.
ultimateAbility
Indicates that an entity possesses or uses its most powerful, defining special ability or move.
-
B.
ultimateEffect
Indicates the final or overall outcome that results from a preceding action, condition, or sequence of events.
-
C.
featuresSpecialAbility
Indicates that an entity possesses or is characterized by a particular special ability.
-
D.
usesPowerType
chosen
Indicates that one entity operates or functions by means of a specified type or source of power.
-
E.
forceAbility
Indicates that one entity has the power or capacity to compel, influence, or cause another entity to act or change in a particular way.
- 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_69f05b08c2008190ac426a035a2ed66d |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65aa8deec8190b1eef143e10c9598 |
completed | May 2, 2026, 8:12 p.m. |
| PD | Predicate disambiguation | batch_69f6576487e081908d802f1caf59c423 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 8:03 a.m.