Triple
T35248467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2009 Winter Universiade |
E1018031
|
entity |
| Predicate | skiVenue |
P39293
|
FINISHED |
| Object | Yabuli Ski Resort |
—
|
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: Yabuli Ski Resort | Statement: [2009 Winter Universiade, skiVenue, Yabuli Ski Resort]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: skiVenue Context triple: [2009 Winter Universiade, skiVenue, Yabuli Ski Resort]
-
A.
outdoorVenue
Indicates that an event, activity, or gathering takes place at a location situated outdoors rather than inside a building or enclosed structure.
-
B.
internationalVenueFor
Indicates that a location serves as a host or site for events, activities, or functions involving participants or audiences from multiple countries.
-
C.
earlyVenue
Indicates that an event or activity takes place at a venue earlier than a standard, expected, or comparative time.
-
D.
venueComplex
Indicates that one venue is a complex or larger facility that contains or encompasses another venue.
-
E.
sportsVenueFor
chosen
Indicates that a venue is used as the location or facility where a particular sport or sporting event takes place.
- 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_69f76de407d081909dfc3c419817ae93 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78f63c8788190b253a18de5ca1312 |
completed | May 3, 2026, 6:09 p.m. |
| PD | Predicate disambiguation | batch_69f78e2d71248190b850c2802ec170c0 |
completed | May 3, 2026, 6:04 p.m. |
Created at: May 3, 2026, 4:02 p.m.