Triple
T3208377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indian Administrative Service |
E67217
|
entity |
| Predicate | cadreType |
P16512
|
FINISHED |
| Object | All India cadre |
—
|
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: All India cadre | Statement: [Indian Administrative Service, cadreType, All India cadre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cadreType Context triple: [Indian Administrative Service, cadreType, All India cadre]
-
A.
cadreSystem
chosen
Indicates a structured system for managing, organizing, and overseeing personnel or leadership positions within an institution or organization.
-
B.
personnelType
Indicates the classification or role category assigned to a person within an organization or system.
-
C.
cadresAllocatedBy
Indicates that specific personnel or staff positions (cadres) are assigned or distributed by a particular authority or organization to another entity.
-
D.
departmentType
Indicates the classification or category of a department, specifying what kind of department it is.
-
E.
typeOfOffice
Indicates the specific category or kind of office that an office entity belongs to (e.g., executive, legislative, judicial, or other office types).
- 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_69ad858ac36c81909962589cd277d6e2 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaa59888481908bdaefa1968d7f04 |
completed | March 8, 2026, 4:56 p.m. |
| PD | Predicate disambiguation | batch_69ad9e078f7c8190813d9fcb4f5071fb |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:07 p.m.