Triple

T859640
Position Surface form Disambiguated ID Type / Status
Subject Tirupati E18570 entity
Predicate municipalCorporationStatus P5556 FINISHED
Object 2012 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: 2012 | Statement: [Tirupati, municipalCorporationStatus, 2012]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: municipalCorporationStatus
Context triple: [Tirupati, municipalCorporationStatus, 2012]
  • A. hasMunicipalStatusChange chosen
    Indicates that an entity undergoes a change in its official municipal status (e.g., creation, upgrade, downgrade, merger, or dissolution as a municipality).
  • B. hasMunicipalGovernment
    Indicates that an entity is administered or governed by a municipal-level governmental authority.
  • C. municipality
    Indicates that one entity is a municipality (a local administrative unit) in which the other entity is located or which it governs.
  • D. hasCouncilAreaStatusFrom
    Indicates that an entity holds council area status starting from a specified point in time.
  • E. hasLocalGovernmentBody
    Indicates that an entity is administered or overseen by a specific local government authority or governing body.
  • 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_69a4938bdd3c8190a954a3c11844d9cf completed March 1, 2026, 7:29 p.m.
NER Named-entity recognition batch_69a4ac50e5ec81908ac0c4b7123b4ebb completed March 1, 2026, 9:14 p.m.
PD Predicate disambiguation batch_69a4aa84835081908aaf98b10656d7d6 completed March 1, 2026, 9:07 p.m.
Created at: March 1, 2026, 7:39 p.m.