Triple
T20204471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kheragarh |
E493312
|
entity |
| Predicate | isTehsilHeadquarters |
P139183
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Kheragarh, isTehsilHeadquarters, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTehsilHeadquarters Context triple: [Kheragarh, isTehsilHeadquarters, true]
-
A.
hasTehsil
Indicates a relationship where an administrative region or district includes or is associated with a specific tehsil (sub-district) within its jurisdiction.
-
B.
isCouncilAreaOf
Indicates that one entity is the officially designated council (local government) area that administers or governs the other entity.
-
C.
hasParentDistrictHeadquarters
Indicates that an administrative district has a specific location designated as its parent (or main) district headquarters.
-
D.
hasCouncilAreaName
Indicates that an entity is associated with a council area identified by a specific name.
-
E.
isDistrictCapitalOf
Indicates that a location serves as the administrative or governmental capital of a specified district.
- F. None of above. chosen
Provenance (4 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_69da6269614c8190bb40475d9d477358 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66d8f90108190b72e37c0056de0f8 |
completed | April 20, 2026, 6:16 p.m. |
| PD | Predicate disambiguation | batch_69e55b14c9d8819095453d0504d9222f |
completed | April 19, 2026, 10:45 p.m. |
| PDg | Predicate description generation | batch_69e56700b1a08190ace53cf95827d72d |
completed | April 19, 2026, 11:36 p.m. |
Created at: April 11, 2026, 11:38 p.m.