Triple
T34543871
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Humanitarian OpenStreetMap Team |
E886871
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | OpenStreetMap community organization |
C20591
|
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: OpenStreetMap community organization Context triple: [Humanitarian OpenStreetMap Team, instanceOf, OpenStreetMap community organization]
-
A.
OSM wiki page
An OSM wiki page is a collaboratively edited documentation page that describes OpenStreetMap concepts, tags, features, and community practices.
-
B.
grassroots organization network
A grassroots organization network is a decentralized alliance of community-based groups that collaborate to mobilize local participation, share resources, and coordinate collective action around shared social, political, or environmental goals.
-
C.
community organisation
chosen
A community organisation is a structured group of people who collaborate locally to address shared needs, interests, or issues and to improve the well-being of their community.
-
D.
Wikimedia organizational structure element
A Wikimedia organizational structure element is a component within the Wikimedia movement’s governance and operational framework, such as committees, affiliates, or roles, that defines responsibilities, decision-making authority, and collaboration pathways.
-
E.
open-source organization
An open-source organization is a collaborative entity that develops, maintains, and governs software or other projects whose source materials are publicly accessible, modifiable, and distributable under open licenses.
- 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_69f349ce5eb881909e431c670944aa68 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:02 a.m.