Triple
T19873570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ICD |
E477580
|
entity |
| Predicate | globalStandardFor |
P34280
|
FINISHED |
| Object | morbidity statistics |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: morbidity statistics | Statement: [ICD, globalStandardFor, morbidity statistics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: globalStandardFor Context triple: [ICD, globalStandardFor, morbidity statistics]
-
A.
jointStandardOf
Indicates that two or more entities share responsibility for defining, maintaining, or adhering to the same standard or set of rules.
-
B.
coreStandard
Indicates that something conforms to, is defined by, or is governed by a central or foundational standard or specification.
-
C.
isStandardOf
chosen
Indicates that something serves as the recognized norm, reference, or benchmark by which another thing is defined, measured, or evaluated.
-
D.
baseStandard
Indicates that one entity serves as the foundational or reference standard upon which another entity is defined, measured, or evaluated.
-
E.
standardizationGoal
Indicates the intended level, outcome, or target state to be achieved through a process of standardization.
- F. None of above.
Provenance (3 batches)
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_69d8e51e7d948190aedbcd6c30361c39 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e658d92f9c8190b363587ed1881c2c |
completed | April 20, 2026, 4:48 p.m. |
| PD | Predicate disambiguation | batch_69e537e8c4e481909fe95d795b4864e7 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:51 p.m.