Triple
T36236886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Government Major Projects Portfolio |
E891399
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | government project portfolio |
C65179
|
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: government project portfolio Context triple: [Government Major Projects Portfolio, instanceOf, government project portfolio]
-
A.
government property portfolio
A government property portfolio is the comprehensive collection and management of all real estate and physical assets owned, leased, or controlled by a government entity to support public services and policy objectives.
-
B.
government procurement program
A government procurement program is a structured system through which public sector entities acquire goods, services, and works from external suppliers in accordance with defined policies, regulations, and budgetary objectives.
-
C.
government-sponsored documentation project
A government-sponsored documentation project is an officially funded and managed initiative to systematically collect, record, and preserve information, data, or cultural materials for public, administrative, or historical purposes.
-
D.
government program category
A government program category is a classification that groups public initiatives, services, or funding efforts based on their shared policy goals, target populations, or functional areas.
-
E.
e-government program
An e-government program is an organized initiative that uses digital technologies to deliver public services, enhance government operations, and improve interaction between government, citizens, and businesses.
- F. None of above. chosen
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_69f76e4387048190a1b27bcbf4ec7423 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:09 p.m.