Triple
T28872819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FHIR Organization |
E732179
|
entity |
| Predicate | contactRepresents |
P170658
|
FINISHED |
| Object | contact persons or departments within the organization |
—
|
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: contact persons or departments within the organization | Statement: [FHIR Organization, contactRepresents, contact persons or departments within the organization]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contactRepresents Context triple: [FHIR Organization, contactRepresents, contact persons or departments within the organization]
-
A.
contactWith
Indicates that two entities are in direct or indirect physical or communicative interaction or touch with each other.
-
B.
contactLanguageWith
Indicates that two entities communicate with each other using a particular language as the medium of contact.
-
C.
worksAsContactFor
chosen
Indicates that one entity serves as the designated contact person or liaison for another entity.
-
D.
technicalContact
Indicates that one entity serves as the primary point of contact for technical issues, support, or maintenance related to another entity.
-
E.
electronicContacts
Indicates that one entity has a means of communicating with another entity via electronic channels (such as email, messaging, or other digital communication methods).
- 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_69fddf721c1481909301a0f379368f10 |
completed | May 8, 2026, 1:04 p.m. |
| PD | Predicate disambiguation | batch_69fddda1ae7c8190b5848ff9a9e39826 |
completed | May 8, 2026, 12:57 p.m. |
Created at: April 28, 2026, 7:34 a.m.