Triple
T26924751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intel Grand Slam |
E677746
|
entity |
| Predicate | eligibleTournamentOrganizer |
P168930
|
FINISHED |
| Object | ESL Pro Tour Masters events |
—
|
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: ESL Pro Tour Masters events | Statement: [Intel Grand Slam, eligibleTournamentOrganizer, ESL Pro Tour Masters events]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eligibleTournamentOrganizer Context triple: [Intel Grand Slam, eligibleTournamentOrganizer, ESL Pro Tour Masters events]
-
A.
competitionOrganizerType
Indicates the specific kind or category of entity responsible for organizing a competition.
-
B.
qualifiedForTournament
Indicates that an entity meets the necessary criteria or requirements to participate in a particular tournament.
-
C.
qualificationOrganizedBy
Indicates that a qualification (such as a course, exam, or certification) is organized or administered by a particular agent or organization.
-
D.
eligibleCompetition
Indicates that an entity meets the required conditions to participate in a particular competition.
-
E.
hasTournament
Indicates that an entity organizes, hosts, or is associated with a specific tournament.
- 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_69eee9bdebc48190ba90a12a63e09c73 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f67866e9248190b7ba218f9ca2ae8d |
completed | May 2, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
| PDg | Predicate description generation | batch_69f676c35f3481909b9ba18a5662d6ce |
completed | May 2, 2026, 10:12 p.m. |
Created at: April 27, 2026, 6:09 a.m.