Triple
T13165714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1998 Winter Paralympics |
E312843
|
entity |
| Predicate | hostCityAlsoHosted |
P66362
|
FINISHED |
| Object | 1998 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: 1998 Winter Olympics | Statement: [1998 Winter Paralympics, hostCityAlsoHosted, 1998 Winter Olympics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostCityAlsoHosted Context triple: [1998 Winter Paralympics, hostCityAlsoHosted, 1998 Winter Olympics]
-
A.
hostCityPreviouslyHosted
chosen
Indicates that the city currently hosting an event has also hosted that same event in one or more previous editions.
-
B.
hostCityOfEvent
Indicates that a city serves as the location where a particular event is held or takes place.
-
C.
hasHostCity
Indicates that a particular event, organization, or activity is located in or officially hosted by a specific city.
-
D.
lastHostCity
Indicates that one entity is the most recent city to have hosted the event or activity associated with the other entity.
-
E.
hasCoHostCity
Indicates that an event is jointly hosted or organized by the specified city alongside one or more other cities.
- 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_69d806ac3ee081909b2fd27d060aa974 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98cf054f88190b05ced98d5a22a62 |
completed | April 10, 2026, 11:51 p.m. |
| PD | Predicate disambiguation | batch_69d98bbd1d088190b7c69f37fc6eeb64 |
completed | April 10, 2026, 11:46 p.m. |
Created at: April 9, 2026, 9:13 p.m.