Triple
T38017501
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | One Public Estate programme |
E948536
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public sector property initiative |
C32458
|
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 sector property initiative Context triple: [One Public Estate programme, instanceOf, public sector property initiative]
-
A.
public sector estate
A public sector estate is the collective portfolio of land, buildings, and infrastructure owned, leased, or managed by government or public bodies to deliver public services and support policy objectives.
-
B.
public sector activity
Public sector activity encompasses all actions, programs, and services carried out by government institutions and publicly funded organizations to fulfill collective needs, implement policies, and promote social and economic welfare.
-
C.
public sector enterprise
A public sector enterprise is an organization owned and operated by the government to provide goods or services, often with broader social or strategic objectives beyond profit.
-
D.
planned sector
A planned sector is a designated area within a city or region that is systematically organized and developed according to a comprehensive plan for land use, infrastructure, and services.
-
E.
public sector portfolio management initiative
chosen
A public sector portfolio management initiative is a coordinated effort by government entities to strategically select, prioritize, and oversee programs and investments to maximize public value, align with policy objectives, and optimize the use of limited resources.
- 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_69f76efc10448190aff5fb566b98f952 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:20 p.m.