Triple
T7031254
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 340B Drug Pricing Program |
E163275
|
entity |
| Predicate | coveredEntityType |
P12345
|
FINISHED |
| Object | disproportionate share hospitals |
—
|
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: disproportionate share hospitals | Statement: [340B Drug Pricing Program, coveredEntityType, disproportionate share hospitals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coveredEntityType Context triple: [340B Drug Pricing Program, coveredEntityType, disproportionate share hospitals]
-
A.
includedEntityType
Indicates that one entity type is contained within, or forms a component part of, another entity type.
-
B.
documentedEntityType
Indicates that an entity has been documented as belonging to a specific type or category.
-
C.
identifiesEntityType
Indicates that one entity specifies or determines the type or category to which another entity belongs.
-
D.
relatedType
Indicates that one entity is connected to another through a specified type or category of relationship.
-
E.
coveredGroup
chosen
Indicates that one group or set is included within, or has its members protected or accounted for by, another group or arrangement.
- 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_69c6885d691c81908cf7d31083113886 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e458ad9c81908c3f492b317ce291 |
completed | March 27, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69c6e1b9a2488190aea351d96afa5a12 |
completed | March 27, 2026, 7:59 p.m. |
Created at: March 27, 2026, 2:35 p.m.