Triple
T5984520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ben Johnson 100 metres disqualification |
E133193
|
entity |
| Predicate | originalTimeStatus |
P67740
|
FINISHED |
| Object | world record |
—
|
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: world record | Statement: [Ben Johnson 100 metres disqualification, originalTimeStatus, world record]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalTimeStatus Context triple: [Ben Johnson 100 metres disqualification, originalTimeStatus, world record]
-
A.
originalReleaseStatus
Indicates the publication or distribution state of a work at the time of its initial release.
-
B.
originalTextStatus
Indicates the relationship between a text and its current state or condition relative to its original, unmodified form.
-
C.
originalIntendedStatus
Indicates the status that was initially planned or expected for an entity before any changes or updates occurred.
-
D.
originalRunStatus
Indicates the initial or prior execution state of a run before any subsequent updates or changes.
-
E.
timeStatus
Indicates the temporal state or condition of an event or entity relative to a reference time (e.g., past, present, future, ongoing, or scheduled).
- 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_69c0087010d081908bb8142342d63330 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04a6c4f2481909cdcf931331b3595 |
completed | March 22, 2026, 8 p.m. |
| PD | Predicate disambiguation | batch_69c049de98648190962b14fd341c93da |
completed | March 22, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69c04a663a4481908983048c69cba6b6 |
completed | March 22, 2026, 8 p.m. |
Created at: March 22, 2026, 4:04 p.m.