Triple
T29485586
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manipur Territorial Council |
E747909
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | former representative governing body |
C1003
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: former representative governing body Context triple: [Manipur Territorial Council, instanceOf, former representative governing body]
-
A.
governing body
A governing body is an organized group of individuals with the authority and responsibility to make decisions, set policies, and oversee the direction and management of an institution, community, or state.
-
B.
former political institution
chosen
A former political institution is an organization or governing body that once held official political authority or administrative power but has since been dissolved, replaced, or rendered inactive.
-
C.
governing body members
Individuals who hold official positions within a governing body and are responsible for making, interpreting, or enforcing policies and decisions on behalf of an organization, community, or state.
-
D.
proposed governmental body
A proposed governmental body is a conceptual organization suggested to perform specific public functions or governance roles, but which has not yet been formally established or granted legal authority.
-
E.
governing body of a Soviet republic
A governing body of a Soviet republic is the central political authority responsible for implementing Communist Party directives, managing state administration, and overseeing economic and social policy within that republic.
- F. None of above.
Provenance (1 batch)
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_69f0bd43ba30819095eb1cfc3adf525c |
completed | April 28, 2026, 1:59 p.m. |
Created at: April 28, 2026, 4:08 p.m.