Triple
T29655343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Forge (StarCraft) |
E750247
|
entity |
| Predicate | controllingPlayer |
P192917
|
FINISHED |
| Object | Protoss player |
—
|
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: Protoss player | Statement: [Forge (StarCraft), controllingPlayer, Protoss player]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controllingPlayer Context triple: [Forge (StarCraft), controllingPlayer, Protoss player]
-
A.
isPlayerControlled
Indicates that an entity is currently being directed or controlled by a human player rather than by the system or AI.
-
B.
decisivePlayPlayer
Indicates that a player made a decisive play that significantly influenced the outcome of a game or match.
-
C.
controllingCharacter
Indicates that one character exerts control, influence, or authority over another character.
-
D.
teamStateControlled
Indicates that a team is under the authority, governance, or regulatory control of a particular state or governmental entity.
-
E.
playableSide
Indicates that a particular side, faction, or team in a game can be actively controlled or chosen by the player.
- 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_69fd32848ea88190a71e6df402bbb30e |
completed | May 8, 2026, 12:47 a.m. |
| PD | Predicate disambiguation | batch_69fd2d7e95588190991d5f21e25155df |
completed | May 8, 2026, 12:25 a.m. |
| PDg | Predicate description generation | batch_69fd328298ac8190b6bd5ded7dca270d |
completed | May 8, 2026, 12:46 a.m. |
Created at: April 28, 2026, 6:54 p.m.