Triple
T21557172
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | President of the Geological Society of London |
E531922
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | learned society leadership position |
C29875
|
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: learned society leadership position Context triple: [President of the Geological Society of London, instanceOf, learned society leadership position]
-
A.
member of learned society
A member of a learned society is an individual formally affiliated with an organization dedicated to advancing a specific academic, scientific, or professional field through research, scholarship, and the exchange of knowledge.
-
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.
office in a learned society
chosen
An office in a learned society is a formal position of responsibility—such as president, secretary, or treasurer—held by a member to help govern, manage, and represent the society’s scholarly activities.
-
D.
seat in learned society
A seat in a learned society is a formally designated membership position, often limited in number, that grants an individual recognized status, rights, and responsibilities within that scholarly organization.
-
E.
seat of learned society
A seat of learned society is the principal location or headquarters where a scholarly or scientific association conducts its core administrative, academic, and ceremonial activities.
- 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_69e0c460232c81908de2c3819d17c00e |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:29 p.m.