Triple
T28872884
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FHIR Encounter |
E732180
|
entity |
| Predicate | hasStatusValue |
P129409
|
FINISHED |
| Object | planned |
—
|
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: planned | Statement: [FHIR Encounter, hasStatusValue, planned]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStatusValue Context triple: [FHIR Encounter, hasStatusValue, planned]
-
A.
hasStatusIn
Indicates that an entity holds or is assigned a particular status within a specified context, scope, or system.
-
B.
hasStatusBasedOn
Indicates that an entity’s status is determined or derived from another condition, event, or entity.
-
C.
hasExistenceStatus
chosen
Indicates that an entity is associated with a particular state of existence, such as being current, historical, planned, or no longer existing.
-
D.
hasStatusInText
Indicates that a particular status or state is explicitly mentioned or described within a given text.
-
E.
hasVariableStatus
Indicates that an entity’s status is not fixed but can change over time or under different conditions.
- 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_69fd783fed9c81909e792702636c4f1f |
completed | May 8, 2026, 5:44 a.m. |
| PD | Predicate disambiguation | batch_69fd7788e63c81909de22fdafcfe41c0 |
completed | May 8, 2026, 5:41 a.m. |
Created at: April 28, 2026, 7:34 a.m.