Triple
T23407680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alpensia Ski Jumping Centre |
E559979
|
entity |
| Predicate | supportsNightEvents |
P43473
|
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: [Alpensia Ski Jumping Centre, supportsNightEvents, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsNightEvents Context triple: [Alpensia Ski Jumping Centre, supportsNightEvents, yes]
-
A.
hasNightRaces
Indicates that the subject hosts or includes races that take place at night.
-
B.
mainEventNight2
Indicates that an event occurs as the primary or featured event during the second night of a sequence or schedule.
-
C.
offersNightlife
chosen
Indicates that a place provides opportunities for nighttime entertainment, such as bars, clubs, or evening events.
-
D.
spendsNight
Indicates that one entity stays overnight or spends the night at the location or with the other entity.
-
E.
nightlifePattern
Indicates a recurring way entities engage in or are associated with nightlife activities, such as typical behaviors, schedules, or participation patterns during night hours.
- 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_69e2454b3a5881909c64773dc8a5d289 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1a50f3f90819084fb682597fee1e1 |
completed | April 29, 2026, 6:28 a.m. |
| PD | Predicate disambiguation | batch_69f061ed34288190a2e5e8cae03b0095 |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:38 p.m.