Triple
T29086629
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FHIR PractitionerRole |
E734133
|
entity |
| Predicate | resourceTypeName |
P60481
|
FINISHED |
| Object | PractitionerRole |
—
|
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: PractitionerRole | Statement: [FHIR PractitionerRole, resourceTypeName, PractitionerRole]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resourceTypeName Context triple: [FHIR PractitionerRole, resourceTypeName, PractitionerRole]
-
A.
referenceType
Indicates the specific kind or category of reference relationship that one entity has to another.
-
B.
primaryResourceType
chosen
Indicates the main or predominant type/category of resource associated with an entity or activity.
-
C.
definitionType
Indicates the specific kind or category of definition that characterizes how one entity is defined in relation to another.
-
D.
conceptualType
Indicates that one entity represents the conceptual category, class, or abstract type to which another entity belongs.
-
E.
representationType
Indicates the specific form or mode in which something is represented or expressed (e.g., as a symbol, image, model, or description).
- 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_69f05b0c0f28819086eae6e84f2ae472 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f66147dd648190893f33542d8d0155 |
completed | May 2, 2026, 8:40 p.m. |
| PD | Predicate disambiguation | batch_69f659d297cc8190b2b962ba30a1edb3 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 11 a.m.