Triple
T28689175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vijayawada district |
E729224
|
entity |
| Predicate | hasHealthcareHub |
P10262
|
FINISHED |
| Object | Vijayawada city |
—
|
NE NERFINISHED |
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: Vijayawada city | Statement: [Vijayawada district, hasHealthcareHub, Vijayawada city]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasHealthcareHub Context triple: [Vijayawada district, hasHealthcareHub, Vijayawada city]
-
A.
hasHealthcareServicesIn
Indicates that a healthcare provider or organization offers or operates healthcare services within a specified location or area.
-
B.
hasHealthcareProvider
Indicates that one entity receives healthcare services or medical oversight from another entity acting as its healthcare provider.
-
C.
hasHealthcareInfrastructure
Indicates that an entity possesses facilities, systems, and resources necessary to deliver healthcare services.
-
D.
hasHealthCareInstitutionType
Indicates that an entity is classified as a specific type or category of healthcare institution.
-
E.
hasMedicalCenter
chosen
Indicates that an entity possesses, hosts, or is associated with a medical center facility.
- 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_69f043e60b6c8190ac2cd042e77fe6e9 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f7516d5b4081908588a6feb541f355 |
completed | May 3, 2026, 1:45 p.m. |
| PD | Predicate disambiguation | batch_69f74d40ebb081909daf60623e38f41d |
completed | May 3, 2026, 1:27 p.m. |
Created at: April 28, 2026, 5:35 a.m.