Triple
T33539749
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sally Pearson |
E859037
|
entity |
| Predicate | setWorldLeadingTime |
P176869
|
FINISHED |
| Object | 12.28 seconds in the 100 metres hurdles in 2011 |
—
|
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: 12.28 seconds in the 100 metres hurdles in 2011 | Statement: [Sally Pearson, setWorldLeadingTime, 12.28 seconds in the 100 metres hurdles in 2011]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setWorldLeadingTime Context triple: [Sally Pearson, setWorldLeadingTime, 12.28 seconds in the 100 metres hurdles in 2011]
-
A.
setWorldBestPerformance
Indicates establishing a new highest recorded performance or record in the world for a given activity or metric.
-
B.
setWorldRecordCompetition
Indicates that an entity achieved a world record performance within the context of a specific competition.
-
C.
setWorldRecordLocation
Indicates the place where a world record was set or achieved.
-
D.
setWorldRecordsIn
Indicates that an entity has achieved and holds world record performances in a specified domain, event, or location.
-
E.
setWorldRecordCount
Indicates the number of times an entity has achieved or set a world record.
- 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_69f3497a5be08190a39b12736899e034 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6f8164698819090c1b471f1caa4c6 |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6632dfc8190af85e258c8519207 |
completed | May 3, 2026, 7:16 a.m. |
| PDg | Predicate description generation | batch_69f6f70b0ca081908b24a98937e6ef66 |
completed | May 3, 2026, 7:19 a.m. |
Created at: May 1, 2026, 1:39 a.m.