Triple
T4171698
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ACM Web Science Conference |
E84578
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | interdisciplinary 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: interdisciplinary conference Context triple: [ACM Web Science Conference, instanceOf, interdisciplinary conference]
-
A.
interdisciplinary hub
An interdisciplinary hub is a collaborative space—physical or virtual—where experts from diverse fields converge to share knowledge, integrate methods, and co-create innovative solutions to complex problems.
-
B.
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.
-
C.
interdisciplinary program
An interdisciplinary program is an academic course of study that integrates methods, perspectives, and content from multiple disciplines to address complex questions or problems that cannot be fully understood through a single field alone.
-
D.
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.
-
E.
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.
- 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_69aed932cab48190b80ffe35f7029ae1 |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:45 p.m.