Triple

T13918910
Position Surface form Disambiguated ID Type / Status
Subject Mir Bakshi E334690 entity
Predicate usedInGovernmentalStructure P23524 FINISHED
Object mansabdari system 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: mansabdari system | Statement: [Mir Bakshi, usedInGovernmentalStructure, mansabdari system]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usedInGovernmentalStructure
Context triple: [Mir Bakshi, usedInGovernmentalStructure, mansabdari system]
  • A. usedInGovernmentBody
    Indicates that an entity is employed by, serves within, or is otherwise functionally involved in the operations of a government body.
  • B. usedInGovernmentIn chosen
    Indicates that something is employed, applied, or functions within the context of a specific government or governmental system.
  • C. inGovernmentStructure
    Indicates that one entity is part of, belongs to, or is included within the organizational or institutional framework of a government.
  • D. basedInGovernmentType
    Indicates that an entity operates within or is associated with a government of a specified governmental system or type.
  • E. locatedInGovernmentBody
    Indicates that an entity is situated within, or is part of, a specific governmental body or institution.
  • 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_69d81c5f739081908bc05b2461f54828 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de272753e48190bc609482635280ff completed April 14, 2026, 11:38 a.m.
PD Predicate disambiguation batch_69de059e4ba881908554f72e889719fa completed April 14, 2026, 9:15 a.m.
Created at: April 9, 2026, 10:16 p.m.