Triple
T17038157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Genting Snow Park |
E413373
|
entity |
| Predicate | openedForCompetition |
P16243
|
FINISHED |
| Object | before 2022 Winter Olympics |
—
|
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: before 2022 Winter Olympics | Statement: [Genting Snow Park, openedForCompetition, before 2022 Winter Olympics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openedForCompetition Context triple: [Genting Snow Park, openedForCompetition, before 2022 Winter Olympics]
-
A.
beganCompetition
Indicates that an entity initiated or started participating in a competitive event or contest involving others.
-
B.
openedForEvent
chosen
Indicates that a venue or location is made accessible and operational specifically for a particular event.
-
C.
hasCompetition
Indicates that one entity is in a state of rivalry or contest with another entity, typically competing for the same goal, resource, or advantage.
-
D.
openingRace
Indicates that one race serves as the initial or first event in a sequence of races or a racing competition.
-
E.
openedDuring
Indicates that an entity began operating, became accessible, or was inaugurated within a specified time period or event.
- 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_69d886cd18288190b006abab23f811b7 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3d8f45f84819092cfb27cc33da026 |
completed | April 18, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69e35d60a588819084f53ef9f8b2e7c0 |
completed | April 18, 2026, 10:30 a.m. |
Created at: April 10, 2026, 5:33 a.m.