Triple
T28872462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FHIR DocumentReference |
E732174
|
entity |
| Predicate | hasDocStatus |
P61374
|
FINISHED |
| Object | preliminary |
—
|
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: preliminary | Statement: [FHIR DocumentReference, hasDocStatus, preliminary]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDocStatus Context triple: [FHIR DocumentReference, hasDocStatus, preliminary]
-
A.
hasDocumentationStatus
Indicates the current state or condition of documentation associated with an entity, such as whether it exists, is complete, or is up to date.
-
B.
DOCStatus
chosen
Indicates the current state or condition of a document within a defined process or lifecycle.
-
C.
hasDOC
Indicates that one entity is associated with, linked to, or possesses a specific document or documentation.
-
D.
hasStatusIn
Indicates that an entity holds or is assigned a particular status within a specified context, scope, or system.
-
E.
documentStatusDeterminedBy
Indicates that the status of a document is determined, set, or influenced by a specific agent, process, or event.
- 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_69f69383222c81909d8baa04129d5c81 |
completed | May 3, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_69f690eb1e948190aab41a89969519a5 |
completed | May 3, 2026, 12:03 a.m. |
Created at: April 28, 2026, 7:34 a.m.