Triple
T36588476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dennis Mitchell |
E902595
|
entity |
| Predicate | personalBestTime |
P185901
|
FINISHED |
| Object | 9.91 seconds in the 100 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: 9.91 seconds in the 100 metres | Statement: [Dennis Mitchell, personalBestTime, 9.91 seconds in the 100 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: personalBestTime Context triple: [Dennis Mitchell, personalBestTime, 9.91 seconds in the 100 metres]
-
A.
personalBest
Indicates that one entity represents the best performance or achievement ever attained personally by another entity.
-
B.
personalBestShortProgramScore
Indicates the highest short program score an individual has ever achieved.
-
C.
personalBestTime_marathon
Indicates that the subject’s recorded time is their fastest (personal best) performance in a marathon event.
-
D.
personalBestShortProgramEvent
Indicates the event in which an individual achieved their personal best score in the short program.
-
E.
personalBest800m
Indicates that an entity holds or represents a person's best performance or fastest recorded time in the 800-meter event.
- 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_69f76e6592e88190bac4eb00a46e9df9 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1baf25c8190a78dd54a400d2c50 |
completed | May 3, 2026, 9:44 p.m. |
| PDg | Predicate description generation | batch_69f7c3705b5c81908c84004543a71c07 |
completed | May 3, 2026, 9:51 p.m. |
Created at: May 3, 2026, 4:11 p.m.