Triple
T38186075
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quake III Arena |
E1005317
|
entity |
| Predicate | esportsTitleFor |
P113830
|
FINISHED |
| Object | Cyberathlete Professional League |
—
|
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: Cyberathlete Professional League | Statement: [Quake III Arena, esportsTitleFor, Cyberathlete Professional League]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: esportsTitleFor Context triple: [Quake III Arena, esportsTitleFor, Cyberathlete Professional League]
-
A.
hasEsportsTitle
Indicates that an entity possesses or has been awarded a specific esports-related title or championship.
-
B.
gameTitle
Indicates the name or title assigned to a particular game in the relationship.
-
C.
esportsTournament
Indicates a competitive event where players or teams participate in organized video game matches under defined rules and structure.
-
D.
sportingTitle
Indicates that one entity holds or is identified by a specific sports-related rank, honor, or championship title in relation to another entity.
-
E.
esportsOrganizer
chosen
Indicates that one entity organizes, manages, or hosts an esports event, competition, or league for another entity.
- 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_69f76dbc22c481908139b694ffde7a0c |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcc42cbac48190b8d3e4c9ce140838 |
completed | May 7, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69fcb0fc69c88190800453eb57a7e62c |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 3, 2026, 4:29 p.m.