Triple
T29605873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Patient Demographics Supplier |
E754574
|
entity |
| Predicate | mayImplementStandard |
P1587
|
FINISHED |
| Object | HL7 v2 PDQ |
—
|
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: HL7 v2 PDQ | Statement: [Patient Demographics Supplier, mayImplementStandard, HL7 v2 PDQ]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayImplementStandard Context triple: [Patient Demographics Supplier, mayImplementStandard, HL7 v2 PDQ]
-
A.
implementedAsStandardBy
Indicates that a standard is put into practice or realized through implementation by a specific entity (such as an organization, system, or component).
-
B.
usesStandard
chosen
Indicates that one entity adopts, follows, or operates according to a specified standard defined by another entity or reference.
-
C.
mayIncludeFeature
Indicates that one entity is allowed or able to contain, incorporate, or be associated with a particular feature.
-
D.
hasStandardImplementation
Indicates that an entity has a defined, commonly accepted implementation that follows an established standard or specification.
-
E.
isPopularStandardFor
Indicates that something is widely accepted and commonly used as the standard choice for a particular purpose or context.
- 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_69f0ef84e5d08190a0df17f5930ceed3 |
completed | April 28, 2026, 5:33 p.m. |
| NER | Named-entity recognition | batch_69f66de7e8948190aa0bfe17808ad8b9 |
completed | May 2, 2026, 9:34 p.m. |
| PD | Predicate disambiguation | batch_69f6659d36208190b01412600a4ed57d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 6:25 p.m.