Triple

T15270254
Position Surface form Disambiguated ID Type / Status
Subject Lumbini Province E365001 entity
Predicate containsDistrict P22582 FINISHED
Object Bardiya District E1039709 NE 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: Bardiya District | Statement: [Lumbini Province, containsDistrict, Bardiya District]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bardiya District
Context triple: [Lumbini Province, containsDistrict, Bardiya District]
  • A. Bardiya District chosen
    Bardiya District is an administrative region in southwestern Nepal known for its rich biodiversity and for encompassing the protected wilderness of Bardia National Park.
  • B. Shatrah District
    Shatrah District is an administrative district in southern Iraq, located within Dhi Qar Governorate and centered around the town of Al-Shatrah.
  • C. Sangi Takht District
    Sangi Takht District is an administrative district located within Afghanistan’s central Daykundi Province.
  • D. Hesarak District
    Hesarak District is an administrative district located in eastern Afghanistan within Nangarhar Province.
  • E. Farsi District
    Farsi District is an administrative district located within Herat Province in western Afghanistan.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d85a0f08408190b3c3259ae35d79d2 completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e0094eac848190a1740ae1aa6b28e0 completed April 15, 2026, 9:55 p.m.
NED1 Entity disambiguation (via context triple) batch_69feef7186d481909067f8088f3ea497 completed May 9, 2026, 8:25 a.m.
Created at: April 10, 2026, 3:14 a.m.