Triple
T14447417
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ACM RecSys |
E358243
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | recommender systems conference |
C11186
|
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: recommender systems conference Context triple: [ACM RecSys, instanceOf, recommender systems conference]
-
A.
neural networks conference
A neural networks conference is a professional gathering where researchers, practitioners, and industry experts present, discuss, and collaborate on the latest advances, applications, and theories in neural network and deep learning technologies.
-
B.
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.
-
C.
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.
-
D.
Konferenz
chosen
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.
natural language processing conference
A natural language processing conference is a formal gathering where researchers, practitioners, and industry professionals present, discuss, and advance methods and applications for computational understanding and generation of human language.
- 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_69d82794dfa081909b9134ad2e32244b |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:19 a.m.