Triple
T567161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Division of Medicinal Chemistry |
E13578
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | subdivision of scientific society |
C1011
|
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: subdivision of scientific society Context triple: [Division of Medicinal Chemistry, instanceOf, subdivision of scientific society]
-
A.
division of a scientific society
chosen
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.
-
B.
learned society
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.
division of IEEE
A division of IEEE is a specialized organizational unit within the Institute of Electrical and Electronics Engineers that focuses on advancing a particular technical field or professional area through standards, publications, conferences, and member activities.
-
D.
academic division
An academic division is a major organizational unit within an educational institution that groups related departments, programs, or disciplines under a common administrative and academic structure.
-
E.
subcommunity
A subcommunity is a smaller, more specialized group of individuals within a larger community who share specific interests, characteristics, or goals that distinguish them from the broader whole.
- 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_69a4933edcf08190b35ecfd6014caee6 |
completed | March 1, 2026, 7:27 p.m. |
Created at: March 1, 2026, 7:33 p.m.