Triple
T3910191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Johann Olav Koss |
E87301
|
entity |
| Predicate | setWorldRecordInEvent |
P34274
|
FINISHED |
| Object | 1500 m speed skating |
—
|
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: 1500 m speed skating | Statement: [Johann Olav Koss, setWorldRecordInEvent, 1500 m speed skating]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setWorldRecordInEvent Context triple: [Johann Olav Koss, setWorldRecordInEvent, 1500 m speed skating]
-
A.
setWorldRecordsIn
chosen
Indicates that an entity has achieved and holds world record performances in a specified domain, event, or location.
-
B.
worldRecordSetOn
Indicates that a world record was achieved or established on a specific date or occasion.
-
C.
wasWorldRecordFor
Indicates that something held the status of being the best performance or highest achievement ever recorded for a particular event, category, or metric at a given time.
-
D.
setWorldRecordCount
Indicates the number of times an entity has achieved or set a world record.
-
E.
isAllTimeRecordHolderFor
Indicates that an entity holds the highest or best performance record of all time for a particular category, event, or metric.
- 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_69aed9424514819086e9c58adde6652d |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef1abe2dc81909c18aeae9b286898 |
completed | March 9, 2026, 4:13 p.m. |
| PD | Predicate disambiguation | batch_69aee75cff148190b6d5979d17fae085 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:22 p.m.