Triple
T24868034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2021 Rugby League World Cup |
E622339
|
entity |
| Predicate | hostCityExamples |
P128457
|
FINISHED |
| Object | Sheffield |
—
|
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: Sheffield | Statement: [2021 Rugby League World Cup, hostCityExamples, Sheffield]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hostCityExamples Context triple: [2021 Rugby League World Cup, hostCityExamples, Sheffield]
-
A.
hostCitiesInclude
chosen
Indicates that a particular set, event, or organization has among its host locations the specified city or cities.
-
B.
hostCityOfEvent
Indicates that a city serves as the location where a particular event is held or takes place.
-
C.
hostCitiesContext
Indicates a contextual relationship in which certain cities serve as hosts for specific events, activities, or entities.
-
D.
hostCityLocatedOn
Indicates that the city serving as a host (e.g., of an event) is geographically situated on or along a specified physical feature or area (such as a river, coast, or region).
-
E.
homeCityOfNOC
Indicates that a given city is the designated home or base city of a particular National Olympic Committee (NOC).
- 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_69e2fac3fdbc81909c2ec49be5743cd9 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f47b865df48190bf4b6d3e9f9305e6 |
completed | May 1, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69f4682c8a3c8190adbfaac99474eaaf |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 18, 2026, 5:23 a.m.