Triple
T33898685
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eliud Kipchoge |
E868985
|
entity |
| Predicate | timeAchieved |
P83896
|
FINISHED |
| Object | 1:59:40 |
—
|
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: 1:59:40 | Statement: [Eliud Kipchoge, timeAchieved, 1:59:40]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeAchieved Context triple: [Eliud Kipchoge, timeAchieved, 1:59:40]
-
A.
achievementTiming
Indicates the temporal relationship specifying when an achievement occurs or is attained relative to other events or a reference time.
-
B.
achievedOn
chosen
Indicates that a particular result, milestone, or state was successfully reached or completed at a specific time or date.
-
C.
goalTimeRecord
Indicates that a specific time value is recorded as the target or goal duration for an activity or process.
-
D.
timeRecorded
Indicates that a specific point or period in time has been captured and stored as associated with an event, action, or state.
-
E.
timeAfterAble
Indicates that one event, state, or action occurs after another point in time at which it becomes possible or permissible.
- 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_69f34997703c8190866b1d404bce531f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7051ad6e4819095e82bbd64761803 |
completed | May 3, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69f700fe24e08190998e2c96fbaaad38 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:48 a.m.