Triple

T20168365
Position Surface form Disambiguated ID Type / Status
Subject Madanapalle E491886 entity
Predicate municipalityGrade P80007 FINISHED
Object selection grade 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: selection grade municipality | Statement: [Madanapalle, municipalityGrade, selection grade municipality]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: municipalityGrade
Context triple: [Madanapalle, municipalityGrade, selection grade municipality]
  • A. municipality
    Indicates that one entity is a municipality (a local administrative unit) in which the other entity is located or which it governs.
  • B. hasMunicipalLevel chosen
    Indicates that an entity is associated with a specific level or tier within a municipal (local government) hierarchy.
  • C. municipalScope
    Indicates that something falls within the authority, jurisdiction, or functional domain of a municipality or local city government.
  • D. municipalKey
    Indicates a unique identifier that links an entity to a specific municipality within an administrative or geographic system.
  • E. hasLocalGovernmentTier
    Indicates that one administrative unit is organized or governed at a specific level within a multi-tier local government structure.
  • 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_69da6266c6888190bc1a3ecf24814d34 completed April 11, 2026, 3:01 p.m.
NER Named-entity recognition batch_69e66845cb588190820c50eea0c40d83 completed April 20, 2026, 5:54 p.m.
PD Predicate disambiguation batch_69e55b0c11cc8190836d1eee5945f000 completed April 19, 2026, 10:45 p.m.
Created at: April 11, 2026, 11:35 p.m.