Triple
T28347383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HIPAA Transactions and Code Sets standards authority |
E717990
|
entity |
| Predicate | codeSetStandard |
P102462
|
FINISHED |
| Object | ICD diagnosis codes |
—
|
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: ICD diagnosis codes | Statement: [HIPAA Transactions and Code Sets standards authority, codeSetStandard, ICD diagnosis codes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: codeSetStandard Context triple: [HIPAA Transactions and Code Sets standards authority, codeSetStandard, ICD diagnosis codes]
-
A.
codeStandard
Indicates that an entity adheres to, complies with, or is governed by a specified coding or programming standard.
-
B.
hasStandardCode
chosen
Indicates that an entity is associated with a recognized standard code that formally identifies or classifies it.
-
C.
codeStandardization
Indicates that multiple pieces of code are being aligned to a common format, style, or set of conventions to ensure consistency.
-
D.
standardNumberStandardizedBy
Indicates that a standard number has been formally defined, approved, or regulated by a specific standardizing authority or organization.
-
E.
scriptUsedForStandardization
Indicates that a particular writing system or script is employed as the standard reference form for normalizing or harmonizing text or data.
- 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_69eff6eb30388190b898b96c4be6f49d |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64c07fdc48190a190bacddf733a46 |
completed | May 2, 2026, 7:10 p.m. |
| PD | Predicate disambiguation | batch_69f641e2f1708190b45b48d6a43c51d2 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 28, 2026, 12:44 a.m.