Triple
T30023353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phoenix (StarCraft) |
E762810
|
entity |
| Predicate | gravitonBeamEffect |
P25626
|
FINISHED |
| Object | lifts ground units into the air |
—
|
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: lifts ground units into the air | Statement: [Phoenix (StarCraft), gravitonBeamEffect, lifts ground units into the air]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gravitonBeamEffect Context triple: [Phoenix (StarCraft), gravitonBeamEffect, lifts ground units into the air]
-
A.
gravityEffect
Indicates the influence one entity’s gravitational force has on another, such as causing attraction, acceleration, or changes in motion.
-
B.
gravityAffected
Indicates that an entity is subject to the force of gravity, causing it to accelerate or move in response to gravitational pull.
-
C.
beam_m
Indicates that one entity directs or projects a beam (such as light, energy, or radiation) toward another entity.
-
D.
containsGraviton
Indicates that one entity includes or is composed of one or more gravitons.
-
E.
beamParticle
chosen
Indicates that one entity directs or projects another entity as a beam-like stream or focused flow.
- 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_69f2246ee6e48190b69e837b913b398a |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f679a8f07c8190bcde0b1bf2a9427a |
completed | May 2, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69f66ec9919881908a187bfc7c4df192 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:48 p.m.