Triple
T38507599
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1995 IIHF World Championship |
E921807
|
entity |
| Predicate | poolDHostCity |
P128457
|
FINISHED |
| Object | Johannesburg |
—
|
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: Johannesburg | Statement: [1995 IIHF World Championship, poolDHostCity, Johannesburg]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: poolDHostCity Context triple: [1995 IIHF World Championship, poolDHostCity, Johannesburg]
-
A.
hostCityCluster
Indicates that a city serves as a central or primary host location within a defined group or cluster of related events, activities, or entities.
-
B.
hostCitiesInclude
chosen
Indicates that a particular set, event, or organization has among its host locations the specified city or cities.
-
C.
hostCitiesContext
Indicates a contextual relationship in which certain cities serve as hosts for specific events, activities, or entities.
-
D.
hostBidCity
Indicates that a city is serving or proposed to serve as the host location for a bid (e.g., for an event, project, or competition).
-
E.
finalHostCity
Indicates the city that ultimately hosts or is selected to host a particular event or competition.
- 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_69f76ea3c5448190aa7002fc1ba3f874 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fcd313e61c8190b174b331365b803f |
completed | May 7, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f6b2e08190bf0300ae7c9ae67a |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:32 p.m.