Triple
T4297382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MedStar Health |
E99746
|
entity |
| Predicate | followsModel |
P26745
|
FINISHED |
| Object | integrated delivery system |
—
|
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: integrated delivery system | Statement: [MedStar Health, followsModel, integrated delivery system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: followsModel Context triple: [MedStar Health, followsModel, integrated delivery system]
-
A.
followsBy
Indicates that one event, state, or entity occurs or comes immediately after another in a sequence or order.
-
B.
follows
Indicates that one entity comes after, moves behind, or acts in accordance with another entity in time, space, or sequence.
-
C.
followsFrom
Indicates that one fact, event, or state logically or causally results from, is implied by, or comes as a consequence of another.
-
D.
followsSystem
chosen
Indicates that one entity adheres to, complies with, or operates according to a particular system, framework, or set of rules defined by another entity.
-
E.
followsUnit
Indicates that one unit comes directly after or is ordered subsequent to another unit in a sequence or structure.
- 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_69b3455175088190aa79c6e03b86647e |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3509bff808190a86fade7ccfc3611 |
completed | March 12, 2026, 11:47 p.m. |
| PD | Predicate disambiguation | batch_69b347fe55a88190b77bab0c0f38e1aa |
completed | March 12, 2026, 11:10 p.m. |
Created at: March 12, 2026, 11:08 p.m.