Triple
T162911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Red Cross and Red Crescent Movement |
E2948
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | global humanitarian network |
C281
|
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: global humanitarian network Context triple: [International Red Cross and Red Crescent Movement, instanceOf, global humanitarian network]
-
A.
global network
A global network is a worldwide interconnected system of communication and information exchange that links devices, organizations, and individuals across international boundaries.
-
B.
international organization
chosen
An international organization is an institutional entity formed by multiple countries or global actors to coordinate policies, manage shared interests, and address transnational issues through cooperative frameworks and agreements.
-
C.
nonprofit organization
A nonprofit organization is an entity formed for purposes other than generating profit, using any surplus revenues to further its mission or public benefit rather than distributing them to owners or shareholders.
-
D.
global computer network
A global computer network is a worldwide system of interconnected computers and devices that communicate using standardized protocols to share data and resources across vast distances.
-
E.
multistakeholder organization
A multistakeholder organization is a collaborative governance structure that brings together diverse actors—such as governments, businesses, civil society, and experts—to jointly make decisions, set standards, or address complex issues of shared concern.
- 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_69a2524ce1e48190ab066bf72859f474 |
completed | Feb. 28, 2026, 2:26 a.m. |
Created at: Feb. 28, 2026, 2:34 a.m.