Triple
T32226138
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nigel Short |
E823207
|
entity |
| Predicate | opponentInWorldChampionshipMatch |
P18497
|
FINISHED |
| Object | Garry Kasparov |
—
|
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: Garry Kasparov | Statement: [Nigel Short, opponentInWorldChampionshipMatch, Garry Kasparov]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opponentInWorldChampionshipMatch Context triple: [Nigel Short, opponentInWorldChampionshipMatch, Garry Kasparov]
-
A.
wasOpponentOf
Indicates that one entity competed or conflicted against another as an adversary in some contest, game, or confrontation.
-
B.
facedOpponent
chosen
Indicates that one entity directly confronted or competed against another as an opponent in a contest, conflict, or challenge.
-
C.
opponentNationality
Indicates that the related entity is the country or nationality of the opponent in a competitive or adversarial context.
-
D.
finalOpponentOf
Indicates that one entity serves as the last or ultimate opponent faced by another entity in a sequence of confrontations or competitions.
-
E.
opponentInCase
Indicates that two parties are on opposing sides in the same legal case or proceeding.
- 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_69f3490b4f948190b99e4f999f5be25f |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6d74b20a48190900dda1014cc13a8 |
completed | May 3, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69f6d26f27dc8190ae426a3e1573933e |
completed | May 3, 2026, 4:43 a.m. |
Created at: May 1, 2026, 12:38 a.m.