Triple
T19436106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Care Everywhere |
E486227
|
entity |
| Predicate | dataTypeExchanged |
P132771
|
FINISHED |
| Object | clinical summaries |
—
|
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: clinical summaries | Statement: [Care Everywhere, dataTypeExchanged, clinical summaries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dataTypeExchanged Context triple: [Care Everywhere, dataTypeExchanged, clinical summaries]
-
A.
dataTypeTransmitted
chosen
Indicates that a specific type or format of data is being sent from one entity to another.
-
B.
changeType
Indicates the specific kind or category of modification that has occurred to an entity or relationship.
-
C.
datumType
Indicates the specific kind or category of data that characterizes or classifies a datum.
-
D.
exchangeType
Indicates the kind or category of exchange occurring between entities, such as the method, direction, or nature of what is being traded or transferred.
-
E.
dataTypes
Indicates that one entity specifies or defines the kinds or formats of data that are valid or expected for another 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_69d8e8d7ad488190a3373045029b0f3b |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6336001488190a05f372779711ed2 |
completed | April 20, 2026, 2:08 p.m. |
| PD | Predicate disambiguation | batch_69e4fd6e806081909053f325ba01ab6b |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:38 p.m.