Triple
T6516425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pia unio |
E148274
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | canonical classification |
C20518
|
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: canonical classification Context triple: [Pia unio, instanceOf, canonical classification]
-
A.
classification board
A classification board is an authoritative body or panel that evaluates and assigns categories, ratings, or classifications to items such as media, products, or information based on defined criteria and standards.
-
B.
social classification
Social classification is the systematic process of categorizing individuals or groups within a society based on attributes such as socioeconomic status, ethnicity, gender, occupation, or education, which shapes their access to resources, power, and opportunities.
-
C.
canonical collection
A canonical collection is an organized set of items or elements arranged in a standard, authoritative form that uniquely represents all relevant variations or instances within a given context.
-
D.
bibliographic classification
A bibliographic classification is a systematic scheme for organizing library and information resources into categories and subcategories to facilitate efficient retrieval and browsing.
-
E.
clinical reference classification
A clinical reference classification is a structured system that organizes medical concepts, diagnoses, procedures, or other health-related information into standardized categories to support consistent documentation, analysis, and communication in healthcare.
- F. None of above. chosen
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_69c687e68e748190baceb9298f32d3ed |
completed | March 27, 2026, 1:36 p.m. |
Created at: March 27, 2026, 1:44 p.m.