Triple
T25331578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Farakka community development block |
E635164
|
entity |
| Predicate | hasGramPanchayat |
P86422
|
FINISHED |
| Object | Bhagabangola |
—
|
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: Bhagabangola | Statement: [Farakka community development block, hasGramPanchayat, Bhagabangola]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGramPanchayat Context triple: [Farakka community development block, hasGramPanchayat, Bhagabangola]
-
A.
hasPanchayatSystem
chosen
Indicates that an entity operates under or is governed by a local self-government structure known as the panchayat system.
-
B.
hasRuralCouncilStatus
Indicates that an entity holds the official designation or legal status of a rural council within a given administrative or governance system.
-
C.
hasTehsil
Indicates a relationship where an administrative region or district includes or is associated with a specific tehsil (sub-district) within its jurisdiction.
-
D.
hasRegionalBoard
Indicates that an entity is overseen, governed, or managed by a specific regional board.
-
E.
hasTownship
Indicates that one administrative area or jurisdiction includes or is associated with a specific township.
- 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_69e75a9908108190a95427a97020632a |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f5f6baf2d48190a6a4cd6501be87d2 |
completed | May 2, 2026, 1:06 p.m. |
| PD | Predicate disambiguation | batch_69f5afd5baac8190bb8ed576813c8591 |
completed | May 2, 2026, 8:03 a.m. |
Created at: April 21, 2026, 1:30 p.m.