Triple

T26227934
Position Surface form Disambiguated ID Type / Status
Subject Rampur Assembly constituency E655946 entity
Predicate assemblySegmentOf P121483 FINISHED
Object Rampur Lok Sabha constituency NE NERFINISHED

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: Rampur Lok Sabha constituency | Statement: [Rampur Assembly constituency, assemblySegmentOf, Rampur Lok Sabha constituency]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: assemblySegmentOf
Context triple: [Rampur Assembly constituency, assemblySegmentOf, Rampur Lok Sabha constituency]
  • A. assemblySegments
    Indicates that an entity is composed of or associated with specific component segments that together form its assembly.
  • B. hasAssemblySegment chosen
    Indicates that an object or system includes a specific segment as part of its overall assembly structure.
  • C. assemblyTerm
    Indicates that an entity is associated with, or occurs during, a specific legislative or organizational assembly term.
  • D. assemblyLinkedTo
    Indicates that one assembly is associated or connected to another assembly in a meaningful or functionally relevant way.
  • E. appearsInSegmentOf
    Indicates that one entity occurs within, or is featured as part of, a specific segment or subsection of another 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_69ee5b4b8b408190993da38c0067cc8d completed April 26, 2026, 6:36 p.m.
NER Named-entity recognition batch_69f61f12b0f08190bc4a16907941864c completed May 2, 2026, 3:58 p.m.
PD Predicate disambiguation batch_69f61b3a8ae0819090189fbd8eb19f2f completed May 2, 2026, 3:41 p.m.
Created at: April 26, 2026, 8:58 p.m.