Triple
T8921734
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deoli taluka |
E212434
|
entity |
| Predicate | hasRuralGovernanceRole |
P81461
|
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: [Deoli taluka, hasRuralGovernanceRole, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRuralGovernanceRole Context triple: [Deoli taluka, hasRuralGovernanceRole, yes]
-
A.
hasRuralCouncilStatus
Indicates that an entity holds the official designation or legal status of a rural council within a given administrative or governance system.
-
B.
hasLocalGovernanceRole
chosen
Indicates that an entity holds an official position or responsibility within a local or municipal governing body.
-
C.
hasRuralDevelopmentDepartment
Indicates that an entity possesses or includes a department responsible for rural development activities or functions.
-
D.
isRuralDistrictOf
Indicates that one administrative area is a rural district that belongs to or is governed as part of another, typically larger, administrative unit.
-
E.
hasRegionalRole
Indicates that an entity holds a specific role, function, or responsibility within a defined geographic region.
- 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_69ca839481d48190b42b037e0d0f636c |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc665024f081909515e02e5f5b2221 |
completed | April 1, 2026, 12:26 a.m. |
| PD | Predicate disambiguation | batch_69cc5ed0ef3c81908cc69eac852ee12a |
completed | March 31, 2026, 11:54 p.m. |
Created at: March 30, 2026, 6:56 p.m.