Triple
T23874916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sri Lanka Administrative Service |
E592837
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public service cadre |
C34320
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: public service cadre Context triple: [Sri Lanka Administrative Service, instanceOf, public service cadre]
-
A.
civil service cadre
chosen
A civil service cadre is a structured group of professional government officials organized by rank, function, and career path to implement public policies and administer state affairs.
-
B.
public service mission
A public service mission is a guiding purpose or mandate focused on delivering benefits, support, or protections to the public or a specific community, typically through government or nonprofit actions that prioritize the common good over private gain.
-
C.
public service system
A public service system is an organized framework of institutions, processes, and resources designed to deliver essential services and support to the public in an efficient, equitable, and transparent manner.
-
D.
headquarters and service regiment
A headquarters and service regiment is a military unit that provides command, control, and essential administrative and logistical support functions for a larger formation or group of subordinate units.
-
E.
public service program
A public service program is an organized initiative, typically funded or supported by government or nonprofit entities, designed to provide services or benefits that address community needs and promote the public good.
- F. None of above.
Provenance (1 batch)
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_69e25d23a5c88190ae3999c70ca15e08 |
completed | April 17, 2026, 4:17 p.m. |
Created at: April 17, 2026, 8:15 p.m.