Triple

T7872872
Position Surface form Disambiguated ID Type / Status
Subject Hyderabad-Karnataka E182779 entity
Predicate hasLinguisticMinority P52733 FINISHED
Object Urdu speakers 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: Urdu speakers | Statement: [Hyderabad-Karnataka, hasLinguisticMinority, Urdu speakers]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasLinguisticMinority
Context triple: [Hyderabad-Karnataka, hasLinguisticMinority, Urdu speakers]
  • A. linguisticMinorityStatus
    Indicates that an entity belongs to a group whose primary language is not the dominant or official language of the surrounding society or region.
  • B. linguisticMinorityIn chosen
    Indicates that a group or population constitutes a linguistic minority within a specified geographic or political region.
  • C. areMinorityLanguagesIn
    Indicates that the subject languages are minority (non-dominant) languages within the specified region, country, or larger linguistic context.
  • D. hasMinorityIn
    Indicates that one entity holds a non-controlling, minority ownership or stake in another entity.
  • E. isOfficialMinorityLanguageIn
    Indicates that a language has formal, legally recognized minority-language status within a specified political or geographic entity.
  • 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_69ca828a17248190b46defe758bc5ad3 completed March 30, 2026, 2:02 p.m.
NER Named-entity recognition batch_69cb39a6d93881908d68386e49bea1e3 completed March 31, 2026, 3:04 a.m.
PD Predicate disambiguation batch_69cae928e1b88190b0620f4c4f03bc7d completed March 30, 2026, 9:20 p.m.
Created at: March 30, 2026, 4:56 p.m.