Triple
T32025105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vishy |
E817796
|
entity |
| Predicate | achievedGrandmasterTitleIn |
P90461
|
FINISHED |
| Object | 1988 |
—
|
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: 1988 | Statement: [Vishy, achievedGrandmasterTitleIn, 1988]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: achievedGrandmasterTitleIn Context triple: [Vishy, achievedGrandmasterTitleIn, 1988]
-
A.
yearAwardedGrandmasterTitle
chosen
Indicates the specific year in which an entity was officially awarded the grandmaster title.
-
B.
FIDEtitle
Indicates that an entity holds a specific official chess title as recognized by FIDE (the International Chess Federation).
-
C.
formerGrandMaster
Indicates that a person once held the title of Grand Master but no longer holds that position.
-
D.
grandMaster
Indicates that one entity holds the highest authoritative or mastery status over a domain, discipline, or organization in relation to another entity.
-
E.
currentGrandMaster
Indicates that one entity is the person who currently holds the title of grand master (e.g., in a game, sport, or organization) with respect to 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_69f348fb04e4819081f4eab040ed7959 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b4694e6c81908bf4f730ddab3fbf |
completed | May 3, 2026, 2:35 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:17 a.m.