Triple
T574715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SIGKDD |
E13737
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ACM special interest group |
C8
|
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: ACM special interest group Context triple: [SIGKDD, instanceOf, ACM special interest group]
-
A.
ACM program
An ACM program is a software application or system developed, evaluated, or used within the context of the Association for Computing Machinery’s computing, research, and educational activities.
-
B.
learned society
chosen
A learned society is an organization that exists to promote an academic discipline or group of related disciplines through research, communication, and professional collaboration among scholars and practitioners.
-
C.
human–computer interaction research center
A human–computer interaction research center is an interdisciplinary organization that studies, designs, and evaluates interactive technologies to improve how people use and experience computer systems.
-
D.
program of the American Society of Civil Engineers
A program of the American Society of Civil Engineers is an organized set of activities, initiatives, or services designed to advance civil engineering knowledge, practice, education, and public welfare in alignment with ASCE’s mission.
-
E.
organizational unit of IEEE
An organizational unit of IEEE is a formally recognized group within the IEEE structure, such as a society, council, region, section, chapter, or committee, that carries out specific professional, technical, or administrative functions in support of IEEE’s mission.
- 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_69a4933fa4d88190a7949cc83c08c5c1 |
completed | March 1, 2026, 7:27 p.m. |
Created at: March 1, 2026, 7:33 p.m.