Triple
T35236833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | India Stack |
E1017399
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | digital public infrastructure |
C3206
|
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: digital public infrastructure Context triple: [India Stack, instanceOf, digital public infrastructure]
-
A.
digital infrastructure company
A digital infrastructure company designs, builds, and operates the foundational technology systems—such as data centers, networks, cloud platforms, and connectivity services—that enable digital applications and services to function reliably and at scale.
-
B.
digital platform
A digital platform is an online infrastructure that facilitates interactions, transactions, or value exchange between users, services, or systems through integrated digital tools and interfaces.
-
C.
digital services organization
A digital services organization is an entity that designs, builds, and operates technology-enabled solutions—such as software platforms, applications, and online services—to deliver value and outcomes for customers and stakeholders.
-
D.
infrastructure
chosen
Infrastructure is the foundational physical and organizational systems—such as transportation, utilities, communication networks, and public facilities—that enable a society or organization to function and grow.
-
E.
digital file-based framework
A digital file-based framework is a structured system that organizes, manages, and processes data and resources primarily through files and directories rather than databases or in-memory structures.
- 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_69f76de12e4c8190bc46b71a32858356 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:02 p.m.