Triple
T768017
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IEEE conferences |
E16217
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | scientific meeting |
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: scientific meeting Context triple: [IEEE conferences, instanceOf, scientific meeting]
-
A.
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.
-
B.
scientific lecture
A scientific lecture is a structured oral presentation in which an expert explains, demonstrates, and contextualizes scientific concepts, methods, or findings to an audience for educational or informational purposes.
-
C.
international scientific programme
An international scientific programme is a coordinated, long-term research initiative involving multiple countries and institutions that collaboratively address shared scientific questions or global challenges.
-
D.
division of a scientific society
A division of a scientific society is a specialized subunit within the society that focuses on a particular discipline, topic, or professional interest, organizing activities, research, and member services related to that area.
-
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_69a49369a0848190af883934cee3db4c |
completed | March 1, 2026, 7:28 p.m. |
Created at: March 1, 2026, 7:37 p.m.