Triple
T10410787
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ICM |
E245382
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | recurring scientific conference |
C26307
|
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: recurring scientific conference Context triple: [ICM, instanceOf, recurring scientific conference]
-
A.
biennial conference
A biennial conference is a large, organized gathering of participants held every two years to share knowledge, present research, and foster collaboration within a specific field or community.
-
B.
annual international conference
An annual international conference is a recurring global event where experts, practitioners, and stakeholders from various regions gather once a year to share research, exchange ideas, and collaborate on topics within a specific field or industry.
-
C.
academic conference
An academic conference is a formal gathering of scholars, researchers, and professionals who present, discuss, and critique original research and developments within a specific field or interdisciplinary area.
-
D.
series of international conferences
chosen
A series of international conferences is a recurring, organized set of global meetings held across different locations and times, bringing together participants from multiple countries to share knowledge, collaborate, and advance a specific field or theme.
-
E.
Konferenz
Eine Konferenz ist eine organisierte, meist zeitlich begrenzte Veranstaltung, bei der mehrere Personen zusammenkommen, um Informationen zu einem bestimmten Thema auszutauschen, zu präsentieren und zu diskutieren.
- F. None of above.
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_69d381be340c8190b05998703d42d224 |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 12:09 p.m.