Triple
T21301497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eunice Barber |
E525074
|
entity |
| Predicate | personalBestHeptathlonPoints |
P98347
|
FINISHED |
| Object | 6861 |
—
|
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: 6861 | Statement: [Eunice Barber, personalBestHeptathlonPoints, 6861]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: personalBestHeptathlonPoints Context triple: [Eunice Barber, personalBestHeptathlonPoints, 6861]
-
A.
olympicBestResult
Indicates the best performance or highest achievement an entity has attained in Olympic competition.
-
B.
personalBestCombinedTotalEvent
chosen
Indicates that the event represents the highest combined total performance an individual has ever achieved across relevant components or disciplines.
-
C.
personalBest
Indicates that one entity represents the best performance or achievement ever attained personally by another entity.
-
D.
worldAthleticsLabel
Indicates that an entity is identified by a specific label or designation as defined by World Athletics.
-
E.
personalBestShortProgramScore
Indicates the highest short program score an individual has ever achieved.
- 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_69e0b517e6748190850d6f6ddf323d69 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e7385cd6308190bf300494833b048f |
completed | April 21, 2026, 8:42 a.m. |
| PD | Predicate disambiguation | batch_69e61612ab748190a72b8703b938abcb |
completed | April 20, 2026, 12:03 p.m. |
Created at: April 16, 2026, 4:05 p.m.