Triple

T12952442
Position Surface form Disambiguated ID Type / Status
Subject Sangrur district E309923 entity
Predicate hasDominantRuralCharacter P47416 FINISHED
Object true 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: true | Statement: [Sangrur district, hasDominantRuralCharacter, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasDominantRuralCharacter
Context triple: [Sangrur district, hasDominantRuralCharacter, true]
  • A. isPredominantlyRural chosen
    Indicates that a place or region is characterized mainly by rural features, such as low population density and extensive non-urban land use.
  • B. hasRuralArea
    Indicates that an entity includes, is associated with, or contains a countryside or sparsely populated geographic area.
  • C. isRural
    Indicates that something is located in, characteristic of, or associated with a countryside or non-urban area.
  • D. hasRuralLocality
    Indicates that an entity possesses, includes, or is associated with a rural locality (such as a village, hamlet, or countryside settlement) within its scope or jurisdiction.
  • E. hasRuralHinterland
    Indicates that a place or urban area is associated with and served by a surrounding rural region that supports it economically, socially, or functionally.
  • 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_69d7bdfb57a88190836b743e2825feca completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d97e59a4c88190907d05b8d57dae89 completed April 10, 2026, 10:48 p.m.
PD Predicate disambiguation batch_69d97dba57988190b786ffed55687a72 completed April 10, 2026, 10:46 p.m.
Created at: April 9, 2026, 5:43 p.m.