Triple
T37333024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2013 FIS Alpine World Ski Championships |
E926803
|
entity |
| Predicate | mainRaceCourse |
P16266
|
FINISHED |
| Object | Planai race course |
—
|
NE NERFINISHED |
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: Planai race course | Statement: [2013 FIS Alpine World Ski Championships, mainRaceCourse, Planai race course]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainRaceCourse Context triple: [2013 FIS Alpine World Ski Championships, mainRaceCourse, Planai race course]
-
A.
hasRacecourse
chosen
Indicates that an entity possesses, contains, or is associated with a racecourse facility or track.
-
B.
racecourseFeature
Indicates that one entity is a physical or functional feature or component of a racecourse associated with the other entity.
-
C.
raceTrack
Indicates that one entity serves as a race track or racing course used by another entity for racing activities.
-
D.
racecourseType
Indicates the specific kind or classification of a racecourse associated with an entity.
-
E.
racecourseSetting
Indicates that an event, scene, or activity takes place in the context or environment of a racecourse.
- 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_69f76eb386d88190a8d511aa11540dfc |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb9e1845e881908d19158440cf3b87 |
completed | May 6, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69fb8d08d6988190a00794ac26078348 |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:16 p.m.