Triple
T25790413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Housing Corporation |
E649531
|
entity |
| Predicate | fundingProgramme |
P5159
|
FINISHED |
| Object | Approved Development Programme |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Approved Development Programme | Statement: [Housing Corporation, fundingProgramme, Approved Development Programme]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fundingProgramme Context triple: [Housing Corporation, fundingProgramme, Approved Development Programme]
-
A.
fundingFramework
Indicates that one entity provides the structural or regulatory basis that governs how funding is allocated, managed, or distributed to another entity or activity.
-
B.
grantProgram
chosen
Indicates that an entity administers or is associated with a structured grant-based funding program.
-
C.
supportingProgram
Indicates that one program provides assistance, resources, or backing to another program or initiative.
-
D.
fundingComponent
Indicates that one entity serves as a financial contributor or funding source for another entity or activity.
-
E.
agencyProgramme
Indicates that an agency is responsible for, manages, or is associated with a particular programme.
- F. None of above.
Provenance (3 batches)
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_69e7ab33e9308190afe415dc6f9e8876 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f603bb02288190b40cedbed5b9651d |
completed | May 2, 2026, 2:01 p.m. |
| PD | Predicate disambiguation | batch_69f602d07590819085ac34b189613104 |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 22, 2026, 5:58 a.m.