Triple
T37671076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belarus and Latvia |
E937957
|
entity |
| Predicate | selectedAsHostsBy |
P188532
|
FINISHED |
| Object | IIHF Congress |
—
|
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: IIHF Congress | Statement: [Belarus and Latvia, selectedAsHostsBy, IIHF Congress]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: selectedAsHostsBy Context triple: [Belarus and Latvia, selectedAsHostsBy, IIHF Congress]
-
A.
hasHosts
Indicates that one entity serves as the host or hosting environment for another entity.
-
B.
typicalHostSelection
Indicates the usual or preferred choice of host entity that is selected in a given context or process.
-
C.
selectedAt
Indicates that an entity was chosen or picked at a specific point in time or under particular selection conditions.
-
D.
areSelectedFor
Indicates that certain entities have been chosen or designated from a larger set for a particular purpose, role, or action.
-
E.
selectedAsSiteFor
Indicates that one entity has been chosen or designated to serve as the location or venue for another entity or activity.
- 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_69f76ed7b1408190ba8c93c53cb8becf |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaa19e4a88190b04f26c0d4e708fd |
completed | May 6, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69fba887821c8190ae93ef1dd389e9c8 |
completed | May 6, 2026, 8:45 p.m. |
| PDg | Predicate description generation | batch_69fba9ddef488190b785d332580650f0 |
completed | May 6, 2026, 8:51 p.m. |
Created at: May 3, 2026, 4:18 p.m.