Triple
T20353758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Umaria railway station |
E496086
|
entity |
| Predicate | hasBasicAmenities |
P79291
|
FINISHED |
| Object | drinking water |
—
|
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: drinking water | Statement: [Umaria railway station, hasBasicAmenities, drinking water]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBasicAmenities Context triple: [Umaria railway station, hasBasicAmenities, drinking water]
-
A.
amenitiesInclude
chosen
Indicates that a place or facility provides or contains specific amenities as part of its features.
-
B.
typicalAmenity
Indicates that something is a common or characteristic amenity typically associated with a given entity or context.
-
C.
hasPassengerAmenity
Indicates that an entity provides or is equipped with a specific amenity intended for the comfort or convenience of its passengers.
-
D.
hasGoodsFacilities
Indicates that a location or entity is equipped with facilities for handling, storing, or processing goods or cargo.
-
E.
hasRegionalAmenity
Indicates that a region provides or contains a specific amenity or facility within its area.
- 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_69e0b4a3f7f48190b37f354574028ca6 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e67851c7088190ba960a33c6dfa824 |
completed | April 20, 2026, 7:02 p.m. |
| PD | Predicate disambiguation | batch_69e57636b4808190bc2855af48a3ccdc |
completed | April 20, 2026, 12:41 a.m. |
Created at: April 16, 2026, 11:25 a.m.