Triple
T26924643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ESL |
E677744
|
entity |
| Predicate | organizesTournamentForGame |
P38960
|
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: [ESL, organizesTournamentForGame, Counter-Strike: Global Offensive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: organizesTournamentForGame Context triple: [ESL, organizesTournamentForGame, Counter-Strike: Global Offensive]
-
A.
organizesGamesFor
Indicates that one entity plans, coordinates, or manages games or gaming activities for another entity.
-
B.
esportsTournament
Indicates a competitive event where players or teams participate in organized video game matches under defined rules and structure.
-
C.
organizesChampionship
Indicates that an entity is responsible for planning, coordinating, and managing the execution of a championship event.
-
D.
esportsOrganizer
Indicates that one entity organizes, manages, or hosts an esports event, competition, or league for another entity.
-
E.
competitionOrganized
chosen
Indicates that an entity is responsible for arranging, managing, or hosting a competition or contest involving other participants.
- 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_69f68805b4848190b75da14996d52a38 |
completed | May 2, 2026, 11:25 p.m. |
| PD | Predicate disambiguation | batch_69f68609c0b08190a8e1238a4d97c270 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 27, 2026, 6:09 a.m.