Triple
T19703883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wikipedia community design process |
E473160
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | consensus-based decision-making process |
C42375
|
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: consensus-based decision-making process Context triple: [Wikipedia community design process, instanceOf, consensus-based decision-making process]
-
A.
órgano de decisión
Un órgano de decisión es una entidad o grupo formalmente constituido dentro de una organización, responsable de analizar información, deliberar y adoptar resoluciones que orientan o determinan su rumbo y funcionamiento.
-
B.
Council decision
A Council decision is a formal, binding resolution adopted by a council body that determines a course of action, policy, or outcome on matters within its authority.
-
C.
intergovernmental consensus
Intergovernmental consensus is a collective agreement reached among multiple governments or states, typically through negotiation and compromise, that establishes a shared position or decision on a specific issue.
-
D.
deliberative assembly
A deliberative assembly is a group of people who meet to discuss, debate, and decide on matters of common concern, typically following formal rules of procedure.
-
E.
committee system
A committee system is an organizational structure in which decision-making and oversight responsibilities are delegated to specialized groups of members who meet, deliberate, and make recommendations or binding decisions within defined areas of authority.
- 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_69d8e516dd048190a0b6c93ea3e71f58 |
completed | April 10, 2026, 11:55 a.m. |
Created at: April 10, 2026, 1:46 p.m.