Triple
T28872311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CDA |
E732171
|
entity |
| Predicate | canUseCodeSystem |
P95403
|
FINISHED |
| Object | SNOMED CT |
—
|
NE NERFINISHED |
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: SNOMED CT | Statement: [CDA, canUseCodeSystem, SNOMED CT]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canUseCodeSystem Context triple: [CDA, canUseCodeSystem, SNOMED CT]
-
A.
standardCodeSystem
chosen
Indicates that an entity uses or is associated with a recognized, authoritative coding or classification system as its reference standard.
-
B.
administrativeCodeSystem
Indicates that there is a system or scheme used to assign and manage administrative codes for organizing or identifying entities or records.
-
C.
regionCodeSystem
Indicates that a region is identified or classified according to a particular coding system for geographic or administrative areas.
-
D.
canUse
Indicates that one entity has the ability, permission, or suitability to make use of another entity or resource.
-
E.
hasStationCodeSystem
Indicates that an entity uses or is associated with a particular system for assigning or managing station codes.
- 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_69f05b06807c81909b4bbd4c20403a2b |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 7:34 a.m.