Triple

T26554252
Position Surface form Disambiguated ID Type / Status
Subject Tehrathum District E671759 entity
Predicate administrativeZoneFormer P96680 FINISHED
Object Koshi Zone 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: Koshi Zone | Statement: [Tehrathum District, administrativeZoneFormer, Koshi Zone]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: administrativeZoneFormer
Context triple: [Tehrathum District, administrativeZoneFormer, Koshi Zone]
  • A. formerNameOfAreaWithin
    Indicates that one area previously had a different name while remaining within the same larger encompassing area.
  • B. formerAdministrativeTerritory chosen
    Indicates that one entity was previously an official administrative territory of another entity but no longer holds that status.
  • C. formerRegionBefore2016
    Indicates that an entity was recognized as a region prior to the year 2016 but no longer holds that regional status after 2016.
  • D. formerMunicipalityOf
    Indicates that an entity was previously an independent municipality that has since been merged into or replaced by the referenced municipality.
  • E. locatedInFormerAdministrativeTerritory
    Indicates that an entity is situated within the boundaries of an administrative territory that no longer exists or has been reorganized.
  • 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_69eeb32163f08190af5f81282738e27a completed April 27, 2026, 12:51 a.m.
NER Named-entity recognition batch_69f6c1265c208190aacd2b551f8f0f82 completed May 3, 2026, 3:29 a.m.
PD Predicate disambiguation batch_69f6bd2415fc81908c23c311aebce66f completed May 3, 2026, 3:12 a.m.
Created at: April 27, 2026, 1:49 a.m.