Triple
T29247309
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terry Bogard |
E741472
|
entity |
| Predicate | superMove |
P180031
|
FINISHED |
| Object | Power Geyser |
—
|
NE NERFINISHED |
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: Power Geyser | Statement: [Terry Bogard, superMove, Power Geyser]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: superMove Context triple: [Terry Bogard, superMove, Power Geyser]
-
A.
superhumanForm
Indicates that an entity has or assumes a form with abilities or attributes that exceed normal human limits.
-
B.
basicMove
Indicates a fundamental movement action performed by or applied to an entity, without specifying any specialized or complex behavior.
-
C.
powerUp
Indicates an action where an entity increases or restores another entity’s energy, strength, or functional capacity.
-
D.
upSpecial
Indicates that an entity performs or is associated with a special upward-directed action or move, often distinct from its normal or default behavior.
-
E.
superSixStage
Indicates that an entity is in or associated with a sixth and particularly advanced or superior stage within a defined multi-stage process or progression.
- F. None of above. chosen
Provenance (4 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_69f0911eba2c8190b07cd2fdf91422c9 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f7308a096081909d66a56f3c926806 |
completed | May 3, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69f72a00c5f081908b6539d15baf4e12 |
completed | May 3, 2026, 10:57 a.m. |
| PDg | Predicate description generation | batch_69f730890a008190a882f7828f1c9162 |
completed | May 3, 2026, 11:24 a.m. |
Created at: April 28, 2026, 12:33 p.m.