Triple

T38030248
Position Surface form Disambiguated ID Type / Status
Subject Dausa Lok Sabha constituency E948887 entity
Predicate constituencyNumberInRajasthan P196612 FINISHED
Object 12 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: 12 | Statement: [Dausa Lok Sabha constituency, constituencyNumberInRajasthan, 12]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: constituencyNumberInRajasthan
Context triple: [Dausa Lok Sabha constituency, constituencyNumberInRajasthan, 12]
  • A. RajasthanAssemblyConstituencyRepresented
    Indicates that a person serves or has served as the elected representative for a specific Rajasthan Legislative Assembly constituency.
  • B. constituencyNumberInMaharashtra
    Indicates the numerical identifier assigned to a specific electoral constituency within the state of Maharashtra.
  • C. assemblyConstituencyNumberInUttarPradesh
    Indicates the specific numerical identifier assigned to an assembly constituency within the state of Uttar Pradesh.
  • D. constituencyNumberInBihar
    Indicates the numerical identifier assigned to a specific electoral constituency within the state of Bihar.
  • E. constituencyNumberInJharkhand
    Indicates the numerical identifier assigned to a specific electoral constituency within the state of Jharkhand.
  • F. None of above. chosen

Provenance (4 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_69f76efd1bc48190a729097fe5177b61 completed May 3, 2026, 3:51 p.m.
NER Named-entity recognition batch_69fe5d58c3e48190910aa3c23485e2c4 completed May 8, 2026, 10:02 p.m.
PD Predicate disambiguation batch_69fe5c92090c8190bcfa412c0a3619df completed May 8, 2026, 9:58 p.m.
PDg Predicate description generation batch_69fe5d580d7c819097cb18d438b01d08 completed May 8, 2026, 10:02 p.m.
Created at: May 3, 2026, 4:20 p.m.