Triple
T4021091
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IEEE International Conference on Data Mining |
E91280
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | data mining conference |
C140
|
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: data mining conference Context triple: [IEEE International Conference on Data Mining, instanceOf, data mining conference]
-
A.
database theory conference
A database theory conference is a formal academic gathering where researchers present and discuss advances in the theoretical foundations of data management, querying, and database systems.
-
B.
computer systems conference
A computer systems conference is a professional gathering where researchers, practitioners, and industry experts present, discuss, and evaluate advances in the design, implementation, and evaluation of computer systems and related technologies.
-
C.
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.
-
D.
academic conference
chosen
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.
-
E.
committee of the Association for Computing Machinery
A committee of the Association for Computing Machinery is a formally organized group of ACM members tasked with overseeing and advancing specific activities, policies, or areas of interest within the computing community.
- 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_69aed9618b04819081750d979d2af098 |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:35 p.m.