Triple
T23049315
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gangneung Curling Centre |
E573963
|
entity |
| Predicate | paralympicVenueFor |
P150784
|
FINISHED |
| Object | wheelchair curling |
—
|
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: wheelchair curling | Statement: [Gangneung Curling Centre, paralympicVenueFor, wheelchair curling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: paralympicVenueFor Context triple: [Gangneung Curling Centre, paralympicVenueFor, wheelchair curling]
-
A.
paralympicHostCity
Indicates that a city has been selected to host a particular edition of the Paralympic Games.
-
B.
OlympicVenue
Indicates that a location serves or has served as a site where official Olympic Games events are held.
-
C.
OlympicVenueType
Indicates the specific type or classification of a venue used for Olympic events.
-
D.
ParalympicSportHosted
Indicates that a particular Paralympic sport was held or staged as part of a specific edition of the Paralympic Games at a given host location.
-
E.
paralympicCounterpartOf
Indicates that one entity is the corresponding Paralympic version or equivalent of another entity, typically an Olympic event, sport, or competition.
- 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_69e245b9c11481909d06c872214d21af |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1867b800881909fabf9dca994c9e7 |
completed | April 29, 2026, 4:18 a.m. |
| PD | Predicate disambiguation | batch_69ef89d5f71881908b9f9d0c8aab278c |
completed | April 27, 2026, 4:07 p.m. |
| PDg | Predicate description generation | batch_69ef9b7494f4819088ae59ea3d0ae8ab |
completed | April 27, 2026, 5:23 p.m. |
Created at: April 17, 2026, 3:54 p.m.