Triple
T30789301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chikhaldara |
E784047
|
entity |
| Predicate | tehsilOf |
P51555
|
FINISHED |
| Object | Amravati district |
—
|
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: Amravati district | Statement: [Chikhaldara, tehsilOf, Amravati district]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tehsilOf Context triple: [Chikhaldara, tehsilOf, Amravati district]
-
A.
hasTehsil
chosen
Indicates a relationship where an administrative region or district includes or is associated with a specific tehsil (sub-district) within its jurisdiction.
-
B.
governmentDistrict
Indicates that a government entity has jurisdiction over or is administratively associated with a specific district.
-
C.
isTehsilHeadquarters
Indicates that a location serves as the administrative headquarters for a tehsil (sub-district) within an administrative division.
-
D.
isCouncilAreaOf
Indicates that one entity is the officially designated council (local government) area that administers or governs the other entity.
-
E.
subdistrictOf
Indicates that one administrative subdistrict is geographically and politically contained within, and is a part of, a larger district.
- 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_69f224b2e2a48190b19aa43db9da5b67 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6900b856881908453d028f34c1e8f |
completed | May 3, 2026, midnight |
| PD | Predicate disambiguation | batch_69f686140aa08190a35f62572b2db9b6 |
completed | May 2, 2026, 11:17 p.m. |
Created at: April 29, 2026, 8:41 p.m.