Triple
T19625307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pulok Chatterji |
E471117
|
entity |
| Predicate | serviceEntryCadre |
P65568
|
FINISHED |
| Object | Uttar Pradesh 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: Uttar Pradesh cadre | Statement: [Pulok Chatterji, serviceEntryCadre, Uttar Pradesh cadre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: serviceEntryCadre Context triple: [Pulok Chatterji, serviceEntryCadre, Uttar Pradesh cadre]
-
A.
cadreSystem
Indicates a structured system for managing, organizing, and overseeing personnel or leadership positions within an institution or organization.
-
B.
jobCadre
chosen
Indicates that an entity belongs to, or is classified within, a particular job cadre or employment category.
-
C.
serviceEntryWith
Indicates that one entity is associated with or accompanied by a particular service entry in a joint or linked context.
-
D.
serviceEntryInROC
Indicates that a service entry is recorded or included in a Register of Companies (ROC) or similar official registry.
-
E.
personnelType
Indicates the classification or role category assigned to a person within an organization or system.
- 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_69d8e510fa248190b7afb274a1d4cf73 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e640e92ff48190ae6e6ba2c603d5e7 |
completed | April 20, 2026, 3:06 p.m. |
| PD | Predicate disambiguation | batch_69e514e5cb108190ae260e466c447314 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:44 p.m.