Triple
T26924753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intel Grand Slam |
E677746
|
entity |
| Predicate | eligibleTournamentType |
P150866
|
FINISHED |
| Object | top-tier international LAN tournaments |
—
|
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: top-tier international LAN tournaments | Statement: [Intel Grand Slam, eligibleTournamentType, top-tier international LAN tournaments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eligibleTournamentType Context triple: [Intel Grand Slam, eligibleTournamentType, top-tier international LAN tournaments]
-
A.
hasTournamentType
chosen
Indicates that a tournament is classified as belonging to a specific type or category (e.g., league, knockout, friendly).
-
B.
eligibleCompetition
Indicates that an entity meets the required conditions to participate in a particular competition.
-
C.
qualifiedForTournament
Indicates that an entity meets the necessary criteria or requirements to participate in a particular tournament.
-
D.
eligibleTournamentOrganizer
Indicates that an entity is qualified and permitted to serve as an organizer for a given tournament.
-
E.
hasTournament
Indicates that an entity organizes, hosts, or is associated with a specific tournament.
- 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_69f67c9fe7b48190b79b4041357edb49 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 27, 2026, 6:09 a.m.