Triple
T32025106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vishy |
E817796
|
entity |
| Predicate | notableGameFormat |
P5812
|
FINISHED |
| Object | rapid 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: rapid chess | Statement: [Vishy, notableGameFormat, rapid chess]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableGameFormat Context triple: [Vishy, notableGameFormat, rapid chess]
-
A.
notableGameType
chosen
Indicates that a game is of a particular type or category for which the subject is especially well known or notable.
-
B.
playedFormat
Indicates that an entity (such as a game, show, or media content) is or was presented, delivered, or experienced in a particular format (such as digital, physical, live, or specific media type).
-
C.
notableGame
Indicates that a particular game is especially significant, prominent, or well-known in relation to the associated entity.
-
D.
gamesPlayedFormat
Indicates the specific format or type of game setup in which the games were played between the related entities.
-
E.
notableGameSupport
Indicates that an entity is recognized for providing significant support or contribution to a particular game.
- 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_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:17 a.m.