Triple
T9284313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Centrepoint |
E223145
|
entity |
| Predicate | charitySector |
P9241
|
FINISHED |
| Object | housing and homelessness |
—
|
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: housing and homelessness | Statement: [Centrepoint, charitySector, housing and homelessness]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: charitySector Context triple: [Centrepoint, charitySector, housing and homelessness]
-
A.
nonProfitSector
Indicates that an entity operates within or is associated with the nonprofit sector, typically focusing on mission-driven rather than profit-driven activities.
-
B.
fieldOfPhilanthropy
chosen
Indicates that an entity is engaged in or associated with a particular area or domain of philanthropic activity.
-
C.
associatedCharity
Indicates that one entity has a formal or recognized charitable affiliation or partnership with another entity.
-
D.
charityComponent
Indicates that one entity functions as a charitable element, feature, or part within another entity or larger arrangement.
-
E.
regionOfPhilanthropy
Indicates the geographic area or location where philanthropic activities, donations, or charitable efforts are directed or take place.
- 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_69ca842123588190b3f2e1a69037d141 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd081e72988190917f425e64631837 |
completed | April 1, 2026, 11:57 a.m. |
| PD | Predicate disambiguation | batch_69cc7a576ec88190bbb787eb82e2e539 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:34 p.m.