Triple
T34308217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paper Church in Kobe |
E880368
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | humanitarian architecture project |
C60609
|
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: humanitarian architecture project Context triple: [Paper Church in Kobe, instanceOf, humanitarian architecture project]
-
A.
humanitarian initiative
A humanitarian initiative is an organized effort or program designed to alleviate human suffering, protect human rights, and improve the well-being of vulnerable or crisis-affected populations.
-
B.
humanitarian planning framework
A humanitarian planning framework is a structured approach that guides the assessment, design, implementation, and evaluation of coordinated actions to meet urgent needs and protect the rights of crisis-affected populations.
-
C.
humanitarian organizations
Humanitarian organizations are entities that provide impartial aid, protection, and support to people affected by crises, disasters, and poverty, aiming to alleviate suffering and uphold human dignity.
-
D.
residential architecture initiative
A residential architecture initiative is a coordinated effort or program focused on planning, designing, and implementing housing solutions that improve the quality, sustainability, and livability of residential environments.
-
E.
affordable housing project
An affordable housing project is a planned development that provides safe, decent, and financially accessible homes to low- and moderate-income individuals or families, often supported by public subsidies or incentives.
- F. None of above. chosen
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_69f349b8bb6c8190ad12a7957a574f04 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 1:57 a.m.