Triple
T30023355
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phoenix (StarCraft) |
E762810
|
entity |
| Predicate | gravitonBeamTargetType |
P3956
|
FINISHED |
| Object | ground units |
—
|
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: ground units | Statement: [Phoenix (StarCraft), gravitonBeamTargetType, ground units]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gravitonBeamTargetType Context triple: [Phoenix (StarCraft), gravitonBeamTargetType, ground units]
-
A.
beamParticle
Indicates that one entity directs or projects another entity as a beam-like stream or focused flow.
-
B.
neutrinoBeamType
Indicates the specific type or classification of a neutrino beam used or produced in an experimental or observational context.
-
C.
beamType
chosen
Indicates the specific kind or category of beam involved in the relationship or action.
-
D.
beam_m
Indicates that one entity directs or projects a beam (such as light, energy, or radiation) toward another entity.
-
E.
beamlineType
Indicates the specific kind or category of beamline associated with an experimental setup or facility.
- 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_69f673c664f08190b4d66cdc305e10db |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 6:48 p.m.