Triple
T37725238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lambardar |
E939699
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | colonial administrative role |
C20737
|
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: colonial administrative role Context triple: [Lambardar, instanceOf, colonial administrative role]
-
A.
colonial-style administrative position
A colonial-style administrative position is a formal role within a governance system modeled on historical colonial administrations, typically involving hierarchical authority over territories, resources, and local populations on behalf of a distant central power.
-
B.
colonial administrative service
A colonial administrative service is a bureaucratic organization established by a colonial power to govern, manage, and implement policies in its overseas territories.
-
C.
instrument of colonial administration
An instrument of colonial administration is any institutional mechanism, policy, or practice deliberately used by a colonial power to govern, control, and extract resources from colonized populations and territories.
-
D.
colonial officer
chosen
A colonial officer is an official appointed by a colonial power to administer, govern, and enforce its policies and interests within a colonized territory.
-
E.
colonial administration period
The colonial administration period is a historical phase during which a foreign imperial power governed a territory through formal political, legal, and bureaucratic structures, often reshaping local institutions, economies, and social relations.
- 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_69f76edc208c8190bc8b9683f75e1024 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:18 p.m.