Triple
T28872818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FHIR Organization |
E732179
|
entity |
| Predicate | partOfLinksTo |
P196243
|
FINISHED |
| Object | parent 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: parent organization | Statement: [FHIR Organization, partOfLinksTo, parent organization]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfLinksTo Context triple: [FHIR Organization, partOfLinksTo, parent organization]
-
A.
relatedToPart
Indicates that one entity has a connection or association with a specific part or component of another entity.
-
B.
textLinkedTo
Indicates that one piece of text is connected or associated with another, such as through a hyperlink, reference, or explicit textual relation.
-
C.
containedPartOf
Indicates that one entity is physically or logically included within and forms a part of another entity.
-
D.
consideredPartOf
Indicates that one entity is regarded or treated as a component, segment, or subset of another entity within a larger whole.
-
E.
partOfType
Indicates that one entity represents a component, segment, or subset that belongs to or is included within the type or category represented by another entity.
- 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_69fe189fec148190aeef51b417ba15b0 |
completed | May 8, 2026, 5:08 p.m. |
| PD | Predicate disambiguation | batch_69fe17285b0881908de7569d8dbd20bd |
completed | May 8, 2026, 5:02 p.m. |
| PDg | Predicate description generation | batch_69fe189f2ea48190b8c4718f1353970e |
completed | May 8, 2026, 5:08 p.m. |
Created at: April 28, 2026, 7:34 a.m.