Triple

T20491417
Position Surface form Disambiguated ID Type / Status
Subject Lahaul sub-division E502753 entity
Predicate instanceOf P0 FINISHED
Object sub-division C18084 CONCEPT FINISHED

How this triple was built (1 step)

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.

CD Concept disambiguation gpt-5-mini-2025-08-07
Target class: sub-division
Context triple: [Lahaul sub-division, instanceOf, sub-division]
  • A. subdivision
    A subdivision is a defined portion of a larger area or entity that has been divided into smaller, distinct parts for organizational, administrative, or functional purposes.
  • B. former subdivision
    A former subdivision is an administrative or territorial unit that once existed as a distinct part of a larger entity but has since been dissolved, merged, or reorganized and no longer functions in its original capacity.
  • C. subdivision of district chosen
    A subdivision of district is an administrative unit that forms a smaller, constituent part of a larger district within a governmental or organizational hierarchy.
  • D. regulatory subdivision
    A regulatory subdivision is a defined geographic or administrative area within a jurisdiction established for the purpose of applying, enforcing, or managing specific regulations, policies, or legal requirements.
  • E. subdivision of court
    A subdivision of court is a distinct organizational unit within a larger judicial system, defined by specific jurisdictional scope, case types, or geographic boundaries.
  • F. None of above.

Provenance (1 batch)

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_69e0b4b0373881909dd3e9387f82eab4 completed April 16, 2026, 10:06 a.m.
Created at: April 16, 2026, 11:35 a.m.