Triple
T13122465
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roman Šebrle |
E311757
|
entity |
| Predicate | personalBestDecathlon |
P98347
|
FINISHED |
| Object | 9026 points |
—
|
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: 9026 points | Statement: [Roman Šebrle, personalBestDecathlon, 9026 points]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: personalBestDecathlon Context triple: [Roman Šebrle, personalBestDecathlon, 9026 points]
-
A.
personalBest
Indicates that one entity represents the best performance or achievement ever attained personally by another entity.
-
B.
personalBestCombinedTotalEvent
chosen
Indicates that the event represents the highest combined total performance an individual has ever achieved across relevant components or disciplines.
-
C.
personalBestShortProgramEvent
Indicates the event in which an individual achieved their personal best score in the short program.
-
D.
olympicBestResult
Indicates the best performance or highest achievement an entity has attained in Olympic competition.
-
E.
personalBestMarathonYear
Indicates the year in which an entity achieved their personal best performance in a marathon.
- 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_69d806a9fe888190b081e2d9ea665d6c |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d9819840b881909b76022b4c4dcaed |
completed | April 10, 2026, 11:02 p.m. |
| PD | Predicate disambiguation | batch_69d98043a74c81908648e6cd0b4c7f71 |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9:07 p.m.