Triple
T23488498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Assam-Meghalaya cadre |
E570605
|
entity |
| Predicate | officerRole |
P16363
|
FINISHED |
| Object | public administration |
—
|
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: public administration | Statement: [Assam-Meghalaya cadre, officerRole, public administration]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officerRole Context triple: [Assam-Meghalaya cadre, officerRole, public administration]
-
A.
officerCategory
Indicates the classification or type of officer role that an individual holds within an organization or system.
-
B.
officersServeAs
Indicates that certain individuals hold and perform the role or duties of officers within a particular organization or context.
-
C.
officersAre
chosen
Indicates that certain individuals hold the role or position of officers within a specified group, organization, or context.
-
D.
notableOfficerRole
Indicates that an entity holds or has held a particularly significant or distinguished officer position within an organization or institution.
-
E.
officerCorps
Indicates that an entity belongs to, is part of, or is associated with a group or body of officers within an organization or institution.
- 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_69e245b0b01481908f636939bedd804c |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a7d9cc08819084c532b069f867ee |
completed | April 29, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69f0620ac3608190b36916261ea50f54 |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 6:04 p.m.