Triple
T25887886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sinhagad Road |
E652240
|
entity |
| Predicate | hasNearbyHealthcareFacilityType |
P75188
|
FINISHED |
| Object | 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: hospitals | Statement: [Sinhagad Road, hasNearbyHealthcareFacilityType, hospitals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyHealthcareFacilityType Context triple: [Sinhagad Road, hasNearbyHealthcareFacilityType, hospitals]
-
A.
hasNearbyFacility
Indicates that one entity is located close to or in the vicinity of a particular facility.
-
B.
nearbyFacilityType
chosen
Indicates that a facility of a specified type is located close to a given reference entity or location.
-
C.
hasCrisisFacility
Indicates that an entity possesses or includes a dedicated facility or service for handling crises or emergency situations.
-
D.
hasNearbyInstitutionType
Indicates that an entity has at least one institution of a specified type located in its nearby geographic vicinity.
-
E.
hasNearbyInfrastructureType
Indicates that an entity is located close to infrastructure of a specified type.
- 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_69e7ab3b92cc81908febd90317862647 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f6d6a6b04c8190bee4cf9c00665ef7 |
completed | May 3, 2026, 5:01 a.m. |
| PD | Predicate disambiguation | batch_69f6d26ceb08819091c71c001e954936 |
completed | May 3, 2026, 4:43 a.m. |
Created at: April 22, 2026, 8:18 a.m.