Triple
T4563388
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Midnapore |
E121849
|
entity |
| Predicate | hasUrbanLocalBodyType |
P10835
|
FINISHED |
| Object | municipality |
—
|
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: municipality | Statement: [Midnapore, hasUrbanLocalBodyType, municipality]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUrbanLocalBodyType Context triple: [Midnapore, hasUrbanLocalBodyType, municipality]
-
A.
isMunicipalCorporationOf
Indicates that an entity functions as the municipal governing body responsible for administering and managing the affairs of a specified city or urban area.
-
B.
hasUrbanClassification
Indicates that an entity is assigned a specific urban status or category within a defined classification system.
-
C.
hasLocalGovernmentBody
Indicates that an entity is administered or overseen by a specific local government authority or governing body.
-
D.
hasMunicipalityType
chosen
Indicates that an administrative unit is classified as having a specific type or category of municipality (e.g., city, town, village).
-
E.
containsUrbanArea
Indicates that a geographic region fully or partially encompasses an urbanized area within its boundaries.
- 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_69bd463f156881908a99aca69c5721ac |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd5830b4308190a63699bf28922375 |
completed | March 20, 2026, 2:22 p.m. |
| PD | Predicate disambiguation | batch_69bd52254c648190a5144cfe8fa7e409 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:09 p.m.