Triple
T29091205
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Grandmaster |
E734856
|
entity |
| Predicate | createdContest |
P139099
|
FINISHED |
| Object | Contest of Champions (Sakaar arena) |
—
|
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: Contest of Champions (Sakaar arena) | Statement: [Grandmaster, createdContest, Contest of Champions (Sakaar arena)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createdContest Context triple: [Grandmaster, createdContest, Contest of Champions (Sakaar arena)]
-
A.
introducedContests
chosen
Indicates that an entity initiated or brought into existence one or more contests or competitive events.
-
B.
losesContestTo
Indicates that one participant is defeated by another in a contest or competition.
-
C.
sponsoredCompetitionOf
Indicates that an entity has provided financial or material support for the organization or execution of a particular competition.
-
D.
competitionRenamedAs
Indicates that a competition previously known by one name is now officially referred to by a different name.
-
E.
titleChallengeEvent
Indicates an event in which a participant competes or acts to obtain, defend, or change a specific title or status.
- 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_69f05b0ed66481908f2e864fa550d2f1 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69fd485f57dc8190820365396d041991 |
completed | May 8, 2026, 2:20 a.m. |
| PD | Predicate disambiguation | batch_69fd47d35da081908bec8901018d186c |
completed | May 8, 2026, 2:17 a.m. |
Created at: April 28, 2026, 11:05 a.m.