Triple
T8527511
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kurnool |
E201854
|
entity |
| Predicate | isMunicipalCorporation |
P46349
|
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: [Kurnool, isMunicipalCorporation, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isMunicipalCorporation Context triple: [Kurnool, isMunicipalCorporation, true]
-
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.
isMunicipal
chosen
Indicates that something belongs to, is administered by, or is characteristic of a municipality or local city government.
-
C.
isMunicipalStatus
Indicates that an entity possesses a specific legally defined municipal status or classification within a governmental or administrative system.
-
D.
hasMunicipalGovernment
Indicates that an entity is administered or governed by a municipal-level governmental authority.
-
E.
isProvincialLevelMunicipality
Indicates that a municipality holds the administrative status and authority of a province-level jurisdiction within a country’s governmental hierarchy.
- 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_69ca83228b24819085d22e7dc99f5d94 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe6477100819081fa20cb6b8ea3d7 |
completed | March 31, 2026, 3:20 p.m. |
| PD | Predicate disambiguation | batch_69cbd10f64b4819080859057c19e58f0 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:16 p.m.