Triple
T15235850
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reference and User Services Association |
E364124
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | library association division |
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: library association division Context triple: [Reference and User Services Association, instanceOf, library association division]
-
A.
library association
A library association is an organized group that supports, advocates for, and advances the interests, standards, and professional development of libraries and library workers.
-
B.
academic association
An academic association is an organized group of scholars, researchers, and professionals dedicated to advancing knowledge, collaboration, and standards within a specific academic discipline or field.
-
C.
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.
-
D.
university association
A university association is an organized group within a higher education institution that brings together students, staff, or alumni around shared academic, professional, cultural, or social interests to provide support, activities, and representation.
-
E.
public association
A public association is a voluntary, non-profit organization formed by individuals or entities to pursue shared interests or goals that serve or involve the broader community.
- 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_69d85a0ce24c81909c4d3b6475548c95 |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:12 a.m.