Triple
T9601611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sergei Bubka |
E231862
|
entity |
| Predicate | personalBestIndoor |
P43521
|
FINISHED |
| Object | 6.15 metres |
—
|
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: 6.15 metres | Statement: [Sergei Bubka, personalBestIndoor, 6.15 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: personalBestIndoor Context triple: [Sergei Bubka, personalBestIndoor, 6.15 metres]
-
A.
personalBest
chosen
Indicates that one entity represents the best performance or achievement ever attained personally by another entity.
-
B.
personalBest_halfMarathon
Indicates that the associated half marathon performance is the best (fastest or highest-achieving) one recorded for the person.
-
C.
olympicBestResult
Indicates the best performance or highest achievement an entity has attained in Olympic competition.
-
D.
isAllTimeRecordHolderFor
Indicates that an entity holds the highest or best performance record of all time for a particular category, event, or metric.
-
E.
worldRecordTime
Indicates that an entity’s recorded time for an event is the fastest ever achieved globally, i.e., the official world record time for that event.
- 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_69ca8484838c8190b2049199d22fef70 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9a3a49608190ad1f65195e4d5cda |
completed | April 1, 2026, 10:20 p.m. |
| PD | Predicate disambiguation | batch_69ccd5a359788190b24f82399489f7fe |
completed | April 1, 2026, 8:21 a.m. |
Created at: March 30, 2026, 8:07 p.m.