Triple
T32025126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vishy |
E817796
|
entity |
| Predicate | EloPeakDate |
P50941
|
FINISHED |
| Object | 2011-03 |
—
|
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: 2011-03 | Statement: [Vishy, EloPeakDate, 2011-03]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: EloPeakDate Context triple: [Vishy, EloPeakDate, 2011-03]
-
A.
ELOmaxRankingDate
Indicates the date on which an entity achieved its highest recorded ELO ranking.
-
B.
ELOminRankingDate
Indicates the date on which an entity’s minimum ELO ranking (its lowest recorded rating position) was reached.
-
C.
EloRating
Indicates a competitive skill rating assigned to an entity, typically updated over time based on performance against other rated entities.
-
D.
powerRating
Indicates the level or amount of power associated with an entity, typically expressing its strength, capacity, or performance capability.
-
E.
peakRatingDate
chosen
Indicates the date on which an entity reached its highest (peak) rating within a given rating history or period.
- 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_69f6b4694e6c81908bf4f730ddab3fbf |
completed | May 3, 2026, 2:35 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:17 a.m.