Triple
T5711708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asafa Powell |
E125924
|
entity |
| Predicate | brokeWorldRecordInEvent |
P42667
|
FINISHED |
| Object | men's 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: men's 100 metres | Statement: [Asafa Powell, brokeWorldRecordInEvent, men's 100 metres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: brokeWorldRecordInEvent Context triple: [Asafa Powell, brokeWorldRecordInEvent, men's 100 metres]
-
A.
wasWorldRecordFor
Indicates that something held the status of being the best performance or highest achievement ever recorded for a particular event, category, or metric at a given time.
-
B.
brokeRecordOf
Indicates that one entity has surpassed or exceeded a previous performance or achievement previously held by another entity.
-
C.
brokeRecord
chosen
Indicates that one entity surpassed a previous best performance or achievement standard set by another (or itself) in a given domain.
-
D.
worldRecordSetOn
Indicates that a world record was achieved or established on a specific date or occasion.
-
E.
setWorldRecordsIn
Indicates that an entity has achieved and holds world record performances in a specified domain, event, or location.
- 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_69c0082d6fe48190b777fb383769e5c8 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c029014588819094a2a0f6f9b66bab |
completed | March 22, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69c021c47f4c81909e6849c3be3e951c |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:46 p.m.