Triple
T19789906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pachmarhi |
E475381
|
entity |
| Predicate | developedAsHillStationBy |
P82014
|
FINISHED |
| Object | British administration |
—
|
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: British administration | Statement: [Pachmarhi, developedAsHillStationBy, British administration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: developedAsHillStationBy Context triple: [Pachmarhi, developedAsHillStationBy, British administration]
-
A.
establishedAsHillStation
chosen
Indicates that a place was formally designated or developed as a hill station, typically for settlement, tourism, or administrative purposes.
-
B.
locatedInHillStation
Indicates that something is situated within or belongs to a geographic area recognized as a hill station.
-
C.
containsHillStation
Indicates that a geographic region or area includes at least one hill station within its boundaries.
-
D.
nearbyHillStation
Indicates that one location is a hill station situated close to another specified place.
-
E.
locatedInHills
Indicates that something is situated within or among hilly terrain or a region characterized by hills.
- 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_69d8e51b014081908b263e167370529a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6538ae5108190b80eb7de6f445f02 |
completed | April 20, 2026, 4:25 p.m. |
| PD | Predicate disambiguation | batch_69e53053ed2881908400becdfada7fd3 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:49 p.m.