Triple
T11956147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C-21A |
E284558
|
entity |
| Predicate | medicalConfigurationCapacity |
P26779
|
FINISHED |
| Object | 1 litter patient |
—
|
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: 1 litter patient | Statement: [C-21A, medicalConfigurationCapacity, 1 litter patient]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: medicalConfigurationCapacity Context triple: [C-21A, medicalConfigurationCapacity, 1 litter patient]
-
A.
numberOfHospitals
Indicates the total count of hospitals associated with a given entity or within a specified context.
-
B.
hasInpatientBeds
Indicates that an entity provides or is equipped with beds designated for admitting and treating inpatients.
-
C.
medicalEvacuationCapacity
chosen
Indicates the ability or resources available to transport and care for patients during a medical evacuation operation.
-
D.
hasHealthcareInfrastructure
Indicates that an entity possesses facilities, systems, and resources necessary to deliver healthcare services.
-
E.
healthSystem
Indicates a relationship where an entity functions as, belongs to, or is managed within a particular health care system or network.
- 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_69d6ab2db38c8190b1f0ed6663ef8ada |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d90366fda8819083168c93abad27d4 |
completed | April 10, 2026, 2:04 p.m. |
| PD | Predicate disambiguation | batch_69d8bb3e48e08190b2fee43af4f57323 |
completed | April 10, 2026, 8:56 a.m. |
Created at: April 8, 2026, 9:45 p.m.