Triple
T22073971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Passport Seva |
E545477
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public service delivery system |
C23643
|
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 delivery system Context triple: [Passport Seva, instanceOf, public service delivery system]
-
A.
public service system
chosen
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.
-
B.
universal service support mechanism
A universal service support mechanism is a regulatory and financial framework designed to ensure that essential communication services are available, affordable, and accessible to all users, including those in high-cost or underserved areas.
-
C.
public emergency service system
A public emergency service system is an integrated network of agencies, communication channels, and response resources that coordinates rapid assistance and protection for the public during crises, disasters, and urgent incidents.
-
D.
through service
A through service is a transportation offering in which a vehicle or passenger travels from origin to destination across one or more intermediate points without requiring a transfer or change of service.
-
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_69e11e344dfc81909b1d88a7221329c7 |
completed | April 16, 2026, 5:36 p.m. |
Created at: April 16, 2026, 8:28 p.m.