Triple
T26995198
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rajasthan Administrative Service |
E679963
|
entity |
| Predicate | serviceCadreLevel |
P14125
|
FINISHED |
| Object | state level |
—
|
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 level | Statement: [Rajasthan Administrative Service, serviceCadreLevel, state level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceCadreLevel Context triple: [Rajasthan Administrative Service, serviceCadreLevel, state level]
-
A.
jobCadre
Indicates that an entity belongs to, or is classified within, a particular job cadre or employment category.
-
B.
designationLevel
chosen
Indicates the specific rank, tier, or level assigned to an entity within a designation or classification system.
-
C.
hasCadre
Indicates that an entity possesses, is assigned, or is supported by a specific group of trained personnel or staff (a cadre).
-
D.
cadreSystem
Indicates a structured system for managing, organizing, and overseeing personnel or leadership positions within an institution or organization.
-
E.
cadresServe
Indicates that designated officials or organizational cadres perform duties or provide services to a group, institution, or cause.
- 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_69eeeb52908c8190bd246244686aa455 |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 27, 2026, 6:54 a.m.