Triple
T28872813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FHIR Organization |
E732179
|
entity |
| Predicate | aliasRepresents |
P132477
|
FINISHED |
| Object | alternate names of 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: alternate names of the organization | Statement: [FHIR Organization, aliasRepresents, alternate names of the organization]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: aliasRepresents Context triple: [FHIR Organization, aliasRepresents, alternate names of the organization]
-
A.
nameRepresents
chosen
Indicates that a given name stands for, denotes, or is used to identify a particular entity.
-
B.
isRepresentiveOf
Indicates that one entity serves as an official agent, spokesperson, or proxy acting on behalf of another entity.
-
C.
areRepresentedBy
Indicates that one entity serves as a representation, proxy, or stand-in for another entity.
-
D.
entityRepresents
Indicates that one entity stands for, symbolizes, or serves as a representation of another entity.
-
E.
memberRepresents
Indicates that one entity serves as an official representative or delegate acting on behalf of another entity within a group, organization, or body.
- 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_69f65a4842588190835ef304e918d03a |
completed | May 2, 2026, 8:10 p.m. |
| PD | Predicate disambiguation | batch_69f65762b5e481908a30ca963dcba4be |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 7:34 a.m.