Triple
T28872817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FHIR Organization |
E732179
|
entity |
| Predicate | activeIndicates |
P15519
|
FINISHED |
| Object | whether the organization record is in active use |
—
|
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: whether the organization record is in active use | Statement: [FHIR Organization, activeIndicates, whether the organization record is in active use]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: activeIndicates Context triple: [FHIR Organization, activeIndicates, whether the organization record is in active use]
-
A.
activeAs
Indicates that an entity is currently functioning or serving in a particular role, capacity, or status.
-
B.
activeWith
Indicates that an entity is currently engaged in or functioning together with another specified entity.
-
C.
activatedAs
Indicates that one entity has been put into an active or operational state in the role or capacity of another specified entity.
-
D.
isActive
chosen
Indicates that an entity is currently functioning, engaged, or enabled within a given context or system.
-
E.
activeAt
Indicates that an entity is functioning, valid, or in effect during a specified time or at a particular location or context.
- 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_69f6cee45590819086e489bfccbe4ac3 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
Created at: April 28, 2026, 7:34 a.m.