Triple
T3766158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2003 World Championships in Athletics |
E82681
|
entity |
| Predicate | hasRaceWalkingEvents |
P50985
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [2003 World Championships in Athletics, hasRaceWalkingEvents, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRaceWalkingEvents Context triple: [2003 World Championships in Athletics, hasRaceWalkingEvents, yes]
-
A.
hasAthletics
Indicates that an entity participates in, is associated with, or offers athletics-related activities or programs.
-
B.
hasRacecourse
Indicates that an entity possesses, contains, or is associated with a racecourse facility or track.
-
C.
raceDayIncludes
Indicates that a particular race day schedule or event set contains or encompasses a specific race or racing-related activity.
-
D.
hasRaceSurface
Indicates that an event or activity takes place on, or is associated with, a specific type of race surface.
-
E.
hasSportingEvent
Indicates that a sporting event is associated with, held at, or organized by a given entity.
- 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_69ad8b207b0081909d2b48843fbd8795 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcc0004608190a810ae0270ae2478 |
completed | March 8, 2026, 7:20 p.m. |
| PD | Predicate disambiguation | batch_69adc04ec36c8190bd5b944d4f4d32aa |
completed | March 8, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69adc133ef50819094c2b971f31f1615 |
completed | March 8, 2026, 6:34 p.m. |
Created at: March 8, 2026, 3:35 p.m.