Triple
T34002474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Huruma |
E871861
|
entity |
| Predicate | hasNGOActivity |
P178142
|
FINISHED |
| Object | slum upgrading projects |
—
|
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: slum upgrading projects | Statement: [Huruma, hasNGOActivity, slum upgrading projects]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNGOActivity Context triple: [Huruma, hasNGOActivity, slum upgrading projects]
-
A.
hasCharityConnection
Indicates a relationship in which one entity is connected to another through charitable activities, support, or affiliation.
-
B.
hasCharitableFunction
Indicates that an entity performs or is designated to perform activities intended for charitable purposes or public benefit.
-
C.
hasCharitableComponent
Indicates that something includes or is associated with a charitable element, such as donations, philanthropy, or support for a charitable cause.
-
D.
hasPoliticalActivityIn
Indicates that an entity engages in or is associated with political activities within a specified location or jurisdiction.
-
E.
nonProfitAffiliation
Indicates that an entity is formally associated with, supported by, or part of a nonprofit organization.
- F. None of above. chosen
Provenance (4 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_69f3499f8cbc81908de6ec89fa91ea8f |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70c53062c8190b4cb7be22ab00bc7 |
completed | May 3, 2026, 8:50 a.m. |
| PD | Predicate disambiguation | batch_69f70abe43e08190b2a30930d96247c1 |
completed | May 3, 2026, 8:43 a.m. |
| PDg | Predicate description generation | batch_69f70b94784c8190970d654e066eb50d |
completed | May 3, 2026, 8:47 a.m. |
Created at: May 1, 2026, 1:50 a.m.