Triple
T29655388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fleet Beacon |
E750248
|
entity |
| Predicate | energySourceLore |
P61281
|
FINISHED |
| Object | Khaydarin crystal-based Protoss technology |
—
|
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: Khaydarin crystal-based Protoss technology | Statement: [Fleet Beacon, energySourceLore, Khaydarin crystal-based Protoss technology]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: energySourceLore Context triple: [Fleet Beacon, energySourceLore, Khaydarin crystal-based Protoss technology]
-
A.
sourceOfPower
chosen
Indicates that one entity serves as the origin or provider of power, energy, or authority for another entity.
-
B.
energySourceDepiction
Indicates that one entity is a visual or symbolic representation of the energy source associated with another entity.
-
C.
usesEnergyFrom
Indicates that one entity derives or consumes energy originating from another entity as its source.
-
D.
outburstEnergySource
Indicates that one entity serves as the source or cause of the energy released in an outburst associated with another entity.
-
E.
energyType
Indicates the kind or category of energy associated with an entity or process.
- 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_69f0d6226fe881908819197c9ef9ee04 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f6b2a65c7c8190ac40f1466ceadefc |
completed | May 3, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f6b14d7d508190bc7d4c89dfba4a32 |
completed | May 3, 2026, 2:22 a.m. |
Created at: April 28, 2026, 6:54 p.m.