Triple
T21792343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RIBA Plan of Work |
E538001
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | construction project process model |
C17006
|
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: construction project process model Context triple: [RIBA Plan of Work, instanceOf, construction project process model]
-
A.
project constitution
A project constitution is a foundational document that formally defines a project's purpose, scope, objectives, stakeholders, governance structure, and guiding principles to align and authorize all subsequent work.
-
B.
infrastructure project
An infrastructure project is a large-scale, organized effort to plan, design, and construct foundational physical systems—such as transportation, utilities, and public facilities—that support a community’s or region’s economic and social activities.
-
C.
unfinished building project
An unfinished building project is a partially constructed structure where work has been halted before completion, leaving it unusable for its intended purpose.
-
D.
project-based mechanism
A project-based mechanism is a structured approach or system in which resources, incentives, and decision-making processes are organized around discrete projects to achieve specific goals or outcomes.
-
E.
engineering process
chosen
An engineering process is a structured, iterative sequence of activities and decisions used to design, develop, test, and maintain systems or products to meet specified requirements efficiently and reliably.
- 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_69e0c47198f881908cb0d237266c10e9 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:52 p.m.