Triple
T20329846
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | David Bedford |
E492445
|
entity |
| Predicate | worldRecordDistance |
P123382
|
FINISHED |
| Object | 10000 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: 10000 metres | Statement: [David Bedford, worldRecordDistance, 10000 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: worldRecordDistance Context triple: [David Bedford, worldRecordDistance, 10000 metres]
-
A.
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.
-
B.
longDistanceRecordTime
Indicates the time value associated with a long-distance record performance or achievement.
-
C.
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.
-
D.
worldRecordType
Indicates that one entity is the category or type of world record associated with another entity.
-
E.
distanceRecord
chosen
Indicates that a specific distance value has been measured, recorded, or maintained between two entities or locations.
- 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_69e0b4a1a09881908d97270d6971a25a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e677e6f5d08190bedf376bbb999ebc |
completed | April 20, 2026, 7 p.m. |
| PD | Predicate disambiguation | batch_69e5762655ac8190a8cc48a29fa2c0c4 |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:22 a.m.