Triple
T9601606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sergei Bubka |
E231862
|
entity |
| Predicate | worldRecordCount |
P89162
|
FINISHED |
| Object | 35 |
—
|
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: 35 | Statement: [Sergei Bubka, worldRecordCount, 35]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worldRecordCount Context triple: [Sergei Bubka, worldRecordCount, 35]
-
A.
worldRecordSet
Indicates that an entity has achieved and established the best performance ever recorded in the world for a particular activity, event, or measurable criterion.
-
B.
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.
-
C.
worldRecordEndDate
Indicates the date on which a particular world record ceased to be valid or was superseded.
-
D.
numberOfOlympicRecords
Indicates the count of Olympic records associated with a given entity.
-
E.
worldRecordSetOn
Indicates that a world record was achieved or established on a specific date or occasion.
- 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_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. |
| PDg | Predicate description generation | batch_69ccd93fc45c8190a823305e461e581d |
completed | April 1, 2026, 8:37 a.m. |
Created at: March 30, 2026, 8:07 p.m.