Triple
T31608992
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paul Keres |
E806572
|
entity |
| Predicate | hasEloPeak |
P180062
|
FINISHED |
| Object | around 2700 (historical estimate) |
—
|
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: around 2700 (historical estimate) | Statement: [Paul Keres, hasEloPeak, around 2700 (historical estimate)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasEloPeak Context triple: [Paul Keres, hasEloPeak, around 2700 (historical estimate)]
-
A.
hasRankAtPeakOfCareer
Indicates the specific rank or position an entity held at the highest point of its career.
-
B.
hasHighestPoints
Indicates that the subject entity possesses the greatest number of points compared to all relevant others in the given context.
-
C.
ELOmaxRankingDate
Indicates the date on which an entity achieved its highest recorded ELO ranking.
-
D.
hasWorldRankingPoints
Indicates that an entity possesses a certain number of points in a global or international ranking system.
-
E.
worldNumberOneRankingAchieved
Indicates that an entity has attained the top position in a recognized world ranking within a specific field or domain.
- 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_69f348d61f2081908cad94bc9ffbb671 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7308a096081909d66a56f3c926806 |
completed | May 3, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69f72a00c5f081908b6539d15baf4e12 |
completed | May 3, 2026, 10:57 a.m. |
| PDg | Predicate description generation | batch_69f730890a008190a882f7828f1c9162 |
completed | May 3, 2026, 11:24 a.m. |
Created at: April 30, 2026, 10:36 p.m.