Triple
T24045601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | digestive health center |
E595508
|
entity |
| Predicate | mayTreatPopulation |
P17586
|
FINISHED |
| Object | pediatric patients |
—
|
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: pediatric patients | Statement: [digestive health center, mayTreatPopulation, pediatric patients]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayTreatPopulation Context triple: [digestive health center, mayTreatPopulation, pediatric patients]
-
A.
targetedPopulation
chosen
Indicates the group of individuals or entities that an action, intervention, or effect is specifically directed toward.
-
B.
supportsPopulation
Indicates that one entity provides the necessary conditions or resources for a population of another entity to exist, persist, or thrive.
-
C.
supportedPopulation
Indicates that one entity provides assistance, resources, or services to sustain or benefit a specified group of people.
-
D.
hasDosingPopulation
Indicates that a specified dosing regimen or information applies to a particular population group.
-
E.
mayPrescribe
Indicates that one entity is authorized or permitted to prescribe something (typically a medication or treatment) to 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_69e288c06a908190899cad4531f32c9a |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d9c9391c819095ea6232fa872d5c |
completed | April 29, 2026, 10:13 a.m. |
| PD | Predicate disambiguation | batch_69f1764345388190a3102b62ddb729b4 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 10:14 p.m.