Triple
T6127085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | All India Services |
E136620
|
entity |
| Predicate | cadreAllocation |
P16512
|
FINISHED |
| Object | state cadres |
—
|
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: state cadres | Statement: [All India Services, cadreAllocation, state cadres]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cadreAllocation Context triple: [All India Services, cadreAllocation, state cadres]
-
A.
cadresAllocatedBy
Indicates that specific personnel or staff positions (cadres) are assigned or distributed by a particular authority or organization to another entity.
-
B.
cadreSystem
chosen
Indicates a structured system for managing, organizing, and overseeing personnel or leadership positions within an institution or organization.
-
C.
corpsAssignment
Indicates that an entity is assigned to serve in or belong to a particular corps or organizational unit.
-
D.
allocationAuthority
Indicates that an entity has the power or right to decide how resources, tasks, or responsibilities are distributed among others.
-
E.
allottedBy
Indicates that something has been assigned, distributed, or allocated by a particular agent or authority.
- 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_69c008a0a37c81908e5b4f879158afb3 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05c2a13a48190b80e11d58fc87c8a |
completed | March 22, 2026, 9:16 p.m. |
| PD | Predicate disambiguation | batch_69c049f9ab3c81909c8ab6466f6a2935 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:15 p.m.