Triple
T36229207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2020 European Women’s Handball Championship |
E891192
|
entity |
| Predicate | originalCoHostCountry |
P99507
|
FINISHED |
| Object | Norway |
E2896
|
NE 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: Norway | Statement: [2020 European Women’s Handball Championship, originalCoHostCountry, Norway]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalCoHostCountry Context triple: [2020 European Women’s Handball Championship, originalCoHostCountry, Norway]
-
A.
coHostCountryWith
Indicates that two countries jointly serve as hosts for the same event or activity.
-
B.
mainHostCountry
Indicates the country that primarily serves as the host location for the associated entity or event.
-
C.
originallyScheduledHostCountry
chosen
Indicates the country that was first designated to host a particular event or activity before any later changes or relocations.
-
D.
originalCoHost
Indicates that an entity served as an initial or first co-host alongside another entity in a shared hosting role.
-
E.
hostedByCountry
Indicates that an event or activity is organized, held, or officially hosted within the jurisdiction of a specific country.
- F. None of above.
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_69f76e4387048190a1b27bcbf4ec7423 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a39a30dbee4819097c0358dd20f471a |
completed | June 22, 2026, 9:03 p.m. |
| PD | Predicate disambiguation | batch_6a037a0a54cc8190868c1bfa1590d1a6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:09 p.m.