Triple
T22340140
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Amsterdam’s civic charities |
E552250
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | poor relief system |
C43236
|
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: poor relief system Context triple: [Amsterdam’s civic charities, instanceOf, poor relief system]
-
A.
public emergency service system
A public emergency service system is an integrated network of agencies, communication channels, and response resources that coordinates rapid assistance and protection for the public during crises, disasters, and urgent incidents.
-
B.
asylum system
The asylum system is the set of laws, institutions, and procedures through which individuals fleeing persecution or serious harm seek and may obtain international protection in a host country.
-
C.
indigent defense system
An indigent defense system is the network of laws, institutions, and services that provides legal representation at public expense to people who cannot afford to hire their own attorneys in criminal proceedings.
-
D.
humanitarian relief operation
A humanitarian relief operation is a coordinated effort to rapidly provide essential aid, services, and protection to populations affected by crises such as natural disasters, conflicts, or epidemics, aiming to save lives, alleviate suffering, and support basic human dignity.
-
E.
welfare facility network
chosen
A welfare facility network is an interconnected system of organizations and service centers that collaboratively provide social support, care, and resources to individuals and communities in need.
- 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_69e11e494eec81909c4d2d51f69499d9 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:43 p.m.