Triple
T28872365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IHE XCA |
E732172
|
entity |
| Predicate | interoperabilityLevel |
P182229
|
FINISHED |
| Object | cross-enterprise |
—
|
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: cross-enterprise | Statement: [IHE XCA, interoperabilityLevel, cross-enterprise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: interoperabilityLevel Context triple: [IHE XCA, interoperabilityLevel, cross-enterprise]
-
A.
interoperabilityStandard
Indicates that there is a standard or specification enabling different systems, components, or technologies to work together and exchange information seamlessly.
-
B.
interoperabilityWith
Indicates that one system, component, or standard can effectively exchange and use information or services with another.
-
C.
isDesignedForInteroperability
Indicates that something is intended or configured to work seamlessly and compatibly with other systems, components, or standards.
-
D.
integrationLevel
Indicates the degree or extent to which two or more entities are combined, interconnected, or function together as a unified whole.
-
E.
interfaceLevel
Indicates the degree or layer at which two systems, components, or entities interact or exchange information through an interface.
- F. None of above. chosen
Provenance (4 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_69f7886be6d8819095ec62e4f2cee858 |
completed | May 3, 2026, 5:39 p.m. |
| PD | Predicate disambiguation | batch_69f7841440f48190b4346c08855951d2 |
completed | May 3, 2026, 5:21 p.m. |
| PDg | Predicate description generation | batch_69f7886b27f08190ab4580f949222c93 |
completed | May 3, 2026, 5:39 p.m. |
Created at: April 28, 2026, 7:34 a.m.