Triple
T35426668
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | England national chess team |
E1023938
|
entity |
| Predicate | FIDEZone |
P182958
|
FINISHED |
| Object | European Chess Union |
—
|
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: European Chess Union | Statement: [England national chess team, FIDEZone, European Chess Union]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: FIDEZone Context triple: [England national chess team, FIDEZone, European Chess Union]
-
A.
FIDEtitle
Indicates that an entity holds a specific official chess title as recognized by FIDE (the International Chess Federation).
-
B.
FIDEWorldChampionshipCycle
Indicates a competitive qualification process or series of events that determine who earns the right to challenge for the FIDE World Chess Championship title.
-
C.
FIDEWorldRanking
Indicates that an entity holds a specific position in the official FIDE world chess rankings at a given time.
-
D.
FIDEID
Indicates that an entity has a specific identification code assigned by the World Chess Federation (FIDE).
-
E.
fideEventCode
Indicates a relationship where an event is assigned or associated with a specific FIDE (chess federation) event code identifier.
- 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_69f76df6704081909900c60be10d5849 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f795933588819082ba3c1716b05d63 |
completed | May 3, 2026, 6:36 p.m. |
| PD | Predicate disambiguation | batch_69f7910770108190bdd39ddb5d304f54 |
completed | May 3, 2026, 6:16 p.m. |
| PDg | Predicate description generation | batch_69f791cad5e08190a8a04ca283dbecaa |
completed | May 3, 2026, 6:19 p.m. |
Created at: May 3, 2026, 4:03 p.m.