Triple
T30233678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grzegorz Komincz |
E768698
|
entity |
| Predicate | playsRaceInStarCraftII |
P167555
|
FINISHED |
| Object | Protoss |
—
|
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: Protoss | Statement: [Grzegorz Komincz, playsRaceInStarCraftII, Protoss]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playsRaceInStarCraftII Context triple: [Grzegorz Komincz, playsRaceInStarCraftII, Protoss]
-
A.
competitiveGame
Indicates a relationship where entities participate in a game or contest in which they compete against each other to win or achieve a higher ranking.
-
B.
featuresRaceBetween
Indicates that an event or context includes or showcases a competitive race occurring between participants.
-
C.
wasBattlegroundRace
Indicates that a particular race or ethnic group was a primary party or side in a conflict or struggle over control, influence, or dominance in a given context.
-
D.
inGameZone
Indicates that an entity is located within a defined game zone or area of the game world.
-
E.
gameRace
chosen
Indicates that an entity participates in or is associated with a race event within a game.
- 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_69f2248108208190be60bf1af343ce70 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6cee45590819086e489bfccbe4ac3 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
Created at: April 29, 2026, 7:37 p.m.