Triple

T29700820
Position Surface form Disambiguated ID Type / Status
Subject Meghalaya Secretariat, Shillong E751475 entity
Predicate stateGovernmentServed P117679 FINISHED
Object Government of Meghalaya 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: Government of Meghalaya | Statement: [Meghalaya Secretariat, Shillong, stateGovernmentServed, Government of Meghalaya]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: stateGovernmentServed
Context triple: [Meghalaya Secretariat, Shillong, stateGovernmentServed, Government of Meghalaya]
  • A. servesStateOrDistrict
    Indicates that an entity holds a role or position in service to a specific state or electoral district.
  • B. governmentServed
    Indicates that a person has held a position serving in or working for a particular government.
  • C. servesPartOfState chosen
    Indicates that an entity serves as an official or functional part of a larger state-level governmental or administrative structure.
  • D. servesStateCapitalRegion
    Indicates that an entity provides services or functions as a service hub for the state capital region.
  • E. stateGovernedWithin
    Indicates that one state exercises governmental authority or control within the territorial or jurisdictional boundaries of another state.
  • 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_69f0d6266f8481909e70bb41cda18587 completed April 28, 2026, 3:45 p.m.
NER Named-entity recognition batch_69fcec5f8b448190b48330a19b462d24 completed May 7, 2026, 7:47 p.m.
PD Predicate disambiguation batch_69fceaf1e23881908ca24160a638e329 completed May 7, 2026, 7:41 p.m.
Created at: April 28, 2026, 7:23 p.m.