Triple
T29655931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DreamHack |
E750262
|
entity |
| Predicate | focusesOnGame |
P31
|
FINISHED |
| Object | Counter-Strike: Global Offensive |
—
|
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: Counter-Strike: Global Offensive | Statement: [DreamHack, focusesOnGame, Counter-Strike: Global Offensive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: focusesOnGame Context triple: [DreamHack, focusesOnGame, Counter-Strike: Global Offensive]
-
A.
homeGamesFocus
Indicates a focus or emphasis on games played at a team's home venue rather than away or neutral-site games.
-
B.
focusesOn
chosen
Indicates that one entity directs its attention, effort, or primary activity toward another entity or specific subject.
-
C.
focusesOnTeam
Indicates that the subject directs attention, effort, or priority toward a particular team as the main area of concern or activity.
-
D.
focusesOnSide
Indicates that an action, attention, or analysis is directed specifically toward one particular side or aspect of something.
-
E.
focusesOnPlatform
Indicates that an entity’s attention, effort, or activity is primarily directed toward a particular platform as its main context or target.
- 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_69f7308a096081909d66a56f3c926806 |
completed | May 3, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69f72a00c5f081908b6539d15baf4e12 |
completed | May 3, 2026, 10:57 a.m. |
Created at: April 28, 2026, 6:55 p.m.