Triple
T30023356
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phoenix (StarCraft) |
E762810
|
entity |
| Predicate | gravitonBeamTacticalUse |
P23064
|
FINISHED |
| Object | battlefield control |
—
|
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: battlefield control | Statement: [Phoenix (StarCraft), gravitonBeamTacticalUse, battlefield control]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gravitonBeamTacticalUse Context triple: [Phoenix (StarCraft), gravitonBeamTacticalUse, battlefield control]
-
A.
tractorBeamStatusOnLaunch
Indicates whether a tractor beam is active or engaged at the moment of launch.
-
B.
usesSpotBeams
Indicates that an entity employs focused, narrow beams (spot beams) to transmit or receive signals or energy.
-
C.
beamUse
chosen
Indicates the action of directing or emitting a beam (such as light, energy, or signal) from one entity toward a target or in a specific direction.
-
D.
usesLaser
Indicates that one entity employs or operates a laser in relation to another entity or context.
-
E.
hasEnergyWeapons
Indicates that an entity is equipped with or uses weapons that emit or manipulate energy (such as lasers or plasma) rather than conventional physical projectiles.
- 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_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 6:48 p.m.