Triple
T24306983
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ordinary IIHF Congress |
E612561
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | IIHF governing body meeting |
C48673
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: IIHF governing body meeting Context triple: [ordinary IIHF Congress, instanceOf, IIHF governing body meeting]
-
A.
continental hockey federation
A continental hockey federation is a governing body that oversees, organizes, and regulates ice hockey activities, competitions, and development programs across multiple countries within a specific continent.
-
B.
IOM governing body session
An IOM governing body session is a formal meeting where the International Organization for Migration’s member states and observers convene to review policies, make strategic decisions, and oversee the organization’s programs and budget.
-
C.
IIHF Hall of Fame induction class
The IIHF Hall of Fame induction class is the annually selected group of players, builders, and officials honored by the International Ice Hockey Federation for their outstanding contributions to international ice hockey.
-
D.
national ice hockey federation
A national ice hockey federation is the governing body responsible for organizing, regulating, and promoting ice hockey within a specific country, including overseeing national teams, leagues, and development programs.
-
E.
FIFA Congress
The FIFA Congress is the supreme legislative and decision-making body of FIFA, comprising representatives from all member associations who convene to set policies, elect officials, and amend regulations governing international football.
- F. None of above. chosen
Provenance (1 batch)
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_69e2d7d91bb48190bc5377d17a85fb21 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 18, 2026, 1:31 a.m.