Triple
T24284728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caster Semenya |
E605638
|
entity |
| Predicate | personalBest800mDate |
P155688
|
FINISHED |
| Object | 2018-07-20 |
—
|
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: 2018-07-20 | Statement: [Caster Semenya, personalBest800mDate, 2018-07-20]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: personalBest800mDate Context triple: [Caster Semenya, personalBest800mDate, 2018-07-20]
-
A.
personalBestMarathon
Indicates that the associated marathon performance is the best (fastest or highest-achieving) marathon result attained by the person in question.
-
B.
personalBest60m
Indicates that an entity has achieved its best-ever performance or record time in a 60-meter event.
-
C.
personalBestTime_marathon
Indicates that the subject’s recorded time is their fastest (personal best) performance in a marathon event.
-
D.
personalBest
Indicates that one entity represents the best performance or achievement ever attained personally by another entity.
-
E.
personalBestMarathonYear
Indicates the year in which an entity achieved their personal best performance in a marathon.
- 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_69e295480d0c8190846fc3c2e2da1d4c |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28f54c5948190a28207d47d6205e4 |
completed | April 29, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69f1c457a2908190993824395b3c365d |
completed | April 29, 2026, 8:41 a.m. |
| PDg | Predicate description generation | batch_69f27a753ca8819095706970d368f762 |
completed | April 29, 2026, 9:39 p.m. |
Created at: April 18, 2026, 12:08 a.m.