Triple
T14861353
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Terry Fox |
E349498
|
entity |
| Predicate | dailyRunningDistance |
P115921
|
FINISHED |
| Object | approximately 42 kilometres |
—
|
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: approximately 42 kilometres | Statement: [Terry Fox, dailyRunningDistance, approximately 42 kilometres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dailyRunningDistance Context triple: [Terry Fox, dailyRunningDistance, approximately 42 kilometres]
-
A.
hasCyclingDistance
Indicates that there is a specified distance associated with traveling between entities by cycling.
-
B.
hourRecordDistanceKm
Indicates the distance in kilometers that was covered or recorded within a one-hour period.
-
C.
hourRecordDistance
Indicates that one entity holds or represents the record for the greatest distance covered within a one-hour time period relative to another entity or context.
-
D.
dailyCycle
Indicates a recurring pattern or process that happens once every day as part of a regular cycle.
-
E.
mainTrackDistance
Indicates the distance measured along the primary or main track between two referenced points or entities.
- 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_69d822ed7e1881909b90fca143ad7e34 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded573cba881908d6d9ac570a64e5f |
completed | April 15, 2026, 12:01 a.m. |
| PD | Predicate disambiguation | batch_69de8c1798c08190b433e9ad21e41a42 |
completed | April 14, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69de8f4b67cc8190b84b59fcec5cf579 |
completed | April 14, 2026, 7:02 p.m. |
Created at: April 10, 2026, 1:54 a.m.