Triple
T30337979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chess960 |
E771671
|
entity |
| Predicate | tournamentUse |
P171582
|
FINISHED |
| Object | used in invitational and championship events |
—
|
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: used in invitational and championship events | Statement: [Chess960, tournamentUse, used in invitational and championship events]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tournamentUse Context triple: [Chess960, tournamentUse, used in invitational and championship events]
-
A.
tournamentOfficiated
Indicates that an entity served as an official (e.g., referee, judge, or umpire) for a particular tournament.
-
B.
tournamentSpecific
Indicates that the relationship, condition, or data applies only within the context of a particular tournament and not generally across other contexts or events.
-
C.
otherTournament
Indicates a relationship where one tournament is distinct from and not the same as another tournament.
-
D.
tournamentMatches
Indicates that a tournament includes or schedules specific matches as part of its competitive structure.
-
E.
competitionUse
Indicates that one entity uses or engages in a competition involving another entity.
- F. None of above. chosen
Provenance (4 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_69f2248aba24819095bb86480d55b23b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6a1ac56b88190a820434b65c9fa23 |
completed | May 3, 2026, 1:15 a.m. |
| PD | Predicate disambiguation | batch_69f69fe463248190aa78128abeab1183 |
completed | May 3, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69f6a0e920cc8190a943fdd0594906c5 |
completed | May 3, 2026, 1:12 a.m. |
Created at: April 29, 2026, 7:54 p.m.