Triple
T14510691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dalilah Muhammad |
E340386
|
entity |
| Predicate | setWorldRecordDate |
P38164
|
FINISHED |
| Object | 2019-07-28 |
—
|
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: 2019-07-28 | Statement: [Dalilah Muhammad, setWorldRecordDate, 2019-07-28]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setWorldRecordDate Context triple: [Dalilah Muhammad, setWorldRecordDate, 2019-07-28]
-
A.
setWorldRecordsIn
Indicates that an entity has achieved and holds world record performances in a specified domain, event, or location.
-
B.
worldRecordSetOn
chosen
Indicates that a world record was achieved or established on a specific date or occasion.
-
C.
setWorldRecordCount
Indicates the number of times an entity has achieved or set a world record.
-
D.
worldRecordSet
Indicates that an entity has achieved and established the best performance ever recorded in the world for a particular activity, event, or measurable criterion.
-
E.
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.
- 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.