Triple
T29655346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Forge (StarCraft) |
E750247
|
entity |
| Predicate | defensiveSynergyWith |
P176327
|
FINISHED |
| Object | Photon Cannon |
—
|
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: Photon Cannon | Statement: [Forge (StarCraft), defensiveSynergyWith, Photon Cannon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defensiveSynergyWith Context triple: [Forge (StarCraft), defensiveSynergyWith, Photon Cannon]
-
A.
defensiveSide
Indicates which entity is acting in a defensive role or position relative to another entity or situation.
-
B.
defensiveSuccess
Indicates that a defensive action successfully prevented or mitigated an opposing threat, attack, or adverse outcome.
-
C.
defensiveSkillEmphasized
Indicates that particular focus or priority is placed on developing or utilizing defensive skills in the relevant context.
-
D.
defensiveRecord
Indicates a relationship where one entity documents, tracks, or summarizes the defensive performance or actions of another entity (such as a player, team, or system).
-
E.
defensiveRole
Indicates that an entity serves a protective or guarding function in relation to another entity or context.
- 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_69f0d6226fe881908819197c9ef9ee04 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f6dfcafd0c81908d86662948c539d6 |
completed | May 3, 2026, 5:40 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
| PDg | Predicate description generation | batch_69f6df418f488190a5e7ff41f32dceda |
completed | May 3, 2026, 5:38 a.m. |
Created at: April 28, 2026, 6:54 p.m.