Triple
T23800845
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tikamgarh railway station |
E588666
|
entity |
| Predicate | hasSanitationFacilities |
P89306
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Tikamgarh railway station, hasSanitationFacilities, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSanitationFacilities Context triple: [Tikamgarh railway station, hasSanitationFacilities, yes]
-
A.
hasCleaningFacility
Indicates that an entity provides or is equipped with a facility or service for cleaning.
-
B.
hasAblutionFacilities
Indicates that an entity provides or is equipped with facilities for performing ablution or ritual washing.
-
C.
sanitationInfrastructure
chosen
Indicates the presence, quality, or extent of facilities and systems designed to safely manage human waste and maintain hygienic environmental conditions.
-
D.
hasDrinkingWaterFacilities
Indicates that a place or facility provides access to safe drinking water sources or infrastructure for people to use.
-
E.
hasLimitedFacilities
Indicates that an entity provides only a restricted or insufficient range or quality of facilities or services.
- 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_69e25d15db58819092ac1e6791696fd9 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c6e0814081908a81e1ede05ab810 |
completed | April 29, 2026, 8:52 a.m. |
| PD | Predicate disambiguation | batch_69f155fe300481909bd617443228df65 |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 7:53 p.m.