Triple
T28872811
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FHIR Organization |
E732179
|
entity |
| Predicate | identifierUsedFor |
P3732
|
FINISHED |
| Object | business identifiers for 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: business identifiers for the organization | Statement: [FHIR Organization, identifierUsedFor, business identifiers for the organization]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: identifierUsedFor Context triple: [FHIR Organization, identifierUsedFor, business identifiers for the organization]
-
A.
designationUsedFor
Indicates that a particular name, label, or title is employed to refer to or identify a specific entity or role.
-
B.
identifiedUsing
Indicates that one entity was recognized, distinguished, or determined by means of a specified method, tool, or identifier.
-
C.
identifierFor
chosen
Indicates that one entity serves as a unique identifying label or code for another entity.
-
D.
nameUsedFor
Indicates that a particular name is used to refer to or designate a given entity.
-
E.
designationUse
Indicates how a particular designation or title is intended to be used or applied in relation to an entity.
- 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_69f66d7765208190b87b1cc6d96a151c |
completed | May 2, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 7:34 a.m.