Triple
T28787515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Southern Maharashtra |
E726855
|
entity |
| Predicate | hasImportantHillStation |
P101854
|
FINISHED |
| Object | Mahabaleshwar |
—
|
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: Mahabaleshwar | Statement: [Southern Maharashtra, hasImportantHillStation, Mahabaleshwar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasImportantHillStation Context triple: [Southern Maharashtra, hasImportantHillStation, Mahabaleshwar]
-
A.
containsHillStation
chosen
Indicates that a geographic region or area includes at least one hill station within its boundaries.
-
B.
establishedAsHillStation
Indicates that a place was formally designated or developed as a hill station, typically for settlement, tourism, or administrative purposes.
-
C.
locatedInHillStation
Indicates that something is situated within or belongs to a geographic area recognized as a hill station.
-
D.
nearbyHillStation
Indicates that one location is a hill station situated close to another specified place.
-
E.
hasMountainStation
Indicates that an entity possesses or is associated with a station located in a mountainous 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_69f0319aabec81908368720196f69a35 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6c1265c208190aacd2b551f8f0f82 |
completed | May 3, 2026, 3:29 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2415fc81908c23c311aebce66f |
completed | May 3, 2026, 3:12 a.m. |
Created at: April 28, 2026, 6:22 a.m.