Triple
T7695128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ABO blood group system |
E174349
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | human blood classification system |
C1782
|
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: human blood classification system Context triple: [ABO blood group system, instanceOf, human blood classification system]
-
A.
health classification system
A health classification system is a structured framework used to categorize and code health-related conditions, statuses, and services for consistent recording, analysis, and decision-making.
-
B.
plant classification system
A plant classification system is an organized framework that categorizes plants into hierarchical groups based on shared characteristics such as morphology, genetics, and evolutionary relationships.
-
C.
medical classification system
chosen
A medical classification system is an organized framework that categorizes diseases, conditions, procedures, and related health information using standardized codes to support diagnosis, treatment, research, and healthcare administration.
-
D.
organ allocation system
An organ allocation system is a coordinated framework of policies, data, and decision-making processes that matches donated organs to recipients based on medical criteria, urgency, compatibility, and ethical guidelines.
-
E.
taxonomic system
A taxonomic system is an organized framework for classifying and naming entities—such as organisms, objects, or concepts—into hierarchical categories based on shared characteristics and relationships.
- 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_69c6995966348190939e6c37ba272c06 |
completed | March 27, 2026, 2:51 p.m. |
Created at: March 27, 2026, 4:02 p.m.