Triple
T29629399
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FHIR |
E755533
|
entity |
| Predicate | supportsTerminology |
—
|
GENERATED |
| Object | SNOMED CT |
—
|
UNRECOGNIZED GENERATED |
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsTerminology Context triple: [FHIR, supportsTerminology, SNOMED CT]
-
A.
isSupportedByLanguage
Indicates that something (such as a feature, format, or construct) is compatible with and can be handled or recognized by a particular language.
-
B.
theorySupports
Indicates that one theory provides justification, evidence, or logical backing for another claim, theory, or proposition.
-
C.
supportedIn
chosen
Indicates that one entity is valid, applicable, or functionally enabled within the context, environment, platform, or scope defined by another entity.
-
D.
supportsTopic
Indicates that one entity provides backing, endorsement, or assistance for a particular topic, idea, or subject.
-
E.
usesLanguageSupport
Indicates that one entity makes use of language-related assistance, features, or services provided by another entity.
- 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_69f0ef88fbe081908f0ad90c1c413f1c |
completed | April 28, 2026, 5:34 p.m. |
Created at: April 28, 2026, 6:40 p.m.