Triple
T14510751
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sifan Hassan |
E340387
|
entity |
| Predicate | personalBest10000m |
P43521
|
FINISHED |
| Object | 29:06.82 |
—
|
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: 29:06.82 | Statement: [Sifan Hassan, personalBest10000m, 29:06.82]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: personalBest10000m Context triple: [Sifan Hassan, personalBest10000m, 29:06.82]
-
A.
personalBestMarathonYear
Indicates the year in which an entity achieved their personal best performance in a marathon.
-
B.
recordHolderMen
Indicates that the subject is the male athlete who holds the record for a specified event or category.
-
C.
longDistanceRecordTime
Indicates the time value associated with a long-distance record performance or achievement.
-
D.
personalBest
chosen
Indicates that one entity represents the best performance or achievement ever attained personally by another entity.
-
E.
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.
- 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_69d822d9c0408190b9a2b3643e58bb4d |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69de94e5b7b48190878be271840c265b |
completed | April 14, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69de5c4ccba08190a988bfda0bc9f5cb |
completed | April 14, 2026, 3:25 p.m. |
Created at: April 10, 2026, 1:21 a.m.