Triple
T32745282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | सशस्त्र सीमा बल |
E837337
|
entity |
| Predicate | कर्मचारी वर्ग |
P11881
|
FINISHED |
| Object | गजेटेड अधिकारी |
—
|
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: गजेटेड अधिकारी | Statement: [सशस्त्र सीमा बल, कर्मचारी वर्ग, गजेटेड अधिकारी]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: कर्मचारी वर्ग Context triple: [सशस्त्र सीमा बल, कर्मचारी वर्ग, गजेटेड अधिकारी]
-
A.
employedPeople
Indicates that there exists a relationship where people are currently working in jobs or positions, typically under an employer.
-
B.
personnelType
chosen
Indicates the classification or role category assigned to a person within an organization or system.
-
C.
commonerClass
Indicates that an entity belongs to the social or economic class of commoners, as opposed to nobility or other privileged groups.
-
D.
eraOfOccupation
Indicates the time period during which an occupation or role was held or practiced.
-
E.
representedEmployeeType
Indicates that one entity serves as a representative or exemplar of a particular type or category of employee for another entity.
- 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_69f34936e1748190b797e406e4e9293a |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6cd126fcc8190aa1f1f146e45ec0c |
completed | May 3, 2026, 4:20 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1470808190b70cdfd7a6395670 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 1:12 a.m.