Triple
T26924696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ESL Gaming |
E677745
|
entity |
| Predicate | organizesCompetitionIn |
P38960
|
FINISHED |
| Object | Counter-Strike 2 |
—
|
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 2 | Statement: [ESL Gaming, organizesCompetitionIn, Counter-Strike 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: organizesCompetitionIn Context triple: [ESL Gaming, organizesCompetitionIn, Counter-Strike 2]
-
A.
competitionOrganized
chosen
Indicates that an entity is responsible for arranging, managing, or hosting a competition or contest involving other participants.
-
B.
organizedCompetitionIn
Indicates that an entity arranged, managed, or hosted a competition that took place in a specified location.
-
C.
competitionOrganizerType
Indicates the specific kind or category of entity responsible for organizing a competition.
-
D.
competitionOrganization
Indicates that an organization is responsible for organizing, hosting, or managing a competition or contest.
-
E.
organizesChampionship
Indicates that an entity is responsible for planning, coordinating, and managing the execution of a championship event.
- 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_69eee9bdebc48190ba90a12a63e09c73 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 27, 2026, 6:09 a.m.