Triple
T3977076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indianization of the officer corps (interwar period) |
E85668
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | recruitment policy |
C9168
|
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: recruitment policy Context triple: [Indianization of the officer corps (interwar period), instanceOf, recruitment policy]
-
A.
organizational policy
chosen
An organizational policy is a formal, guiding principle or rule established by an organization to direct decisions, behaviors, and procedures in alignment with its goals, values, and legal obligations.
-
B.
anti-discrimination policy
An anti-discrimination policy is an organizational rule set that prohibits unfair treatment of individuals or groups based on protected characteristics and outlines procedures for prevention, reporting, and remediation of discriminatory behavior.
-
C.
recruitment poster
A recruitment poster is a visually striking printed or digital advertisement designed to attract and motivate individuals to join an organization, cause, or activity by highlighting its benefits, values, and opportunities.
-
D.
online recruitment platform
An online recruitment platform is a digital system that connects employers and job seekers by enabling job postings, candidate search, application management, and communication throughout the hiring process.
-
E.
language policy
Language policy is the set of deliberate decisions, principles, and regulations by which authorities or institutions influence the status, use, structure, and learning of one or more languages within a society.
- 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_69aed93908348190a26c8aaf4fab3e86 |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:33 p.m.