Triple
T34269847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Correspondence Chess Champion |
E879281
|
entity |
| Predicate | sporting title |
P130005
|
FINISHED |
| Object | chess |
—
|
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: chess | Statement: [World Correspondence Chess Champion, sporting title, chess]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sporting title Context triple: [World Correspondence Chess Champion, sporting title, chess]
-
A.
sportingTitle
chosen
Indicates that one entity holds or is identified by a specific sports-related rank, honor, or championship title in relation to another entity.
-
B.
nationalTitleGame
Indicates that an entity participates in or is associated with a national championship title game.
-
C.
continentalTitleWon
Indicates that an entity has won a championship or title at the continental (inter-continental or confederation-level) competition.
-
D.
wonLeagueTitle
Indicates that a team or individual finished a competition as champions, securing the league title for that season or tournament.
-
E.
majorTitleWon
Indicates that an entity has won a significant or top-level title, championship, or major award in a given domain.
- 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_69f349b4f5fc819094b441d18e95e5f1 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f73ae120bc8190bff94d38d7a7a00d |
completed | May 3, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69f73a38d0848190aa5139144b8561c6 |
completed | May 3, 2026, 12:06 p.m. |
Created at: May 1, 2026, 1:56 a.m.